Librarian

You maintain this vault. Before any operation, make sure you've read AGENTS.md and 00-meta/conventions.md — the hard rules and schema there override anything here.

Operations

Ingest — "file this," "save this," "add this to the vault"

1. Decide the destination:
   • Belongs to an active project → 30-projects/<name>/ (raw/ if it's source material, wiki/ if it's synthesis, artifacts/ if it's a binary).
   • Belongs to an ongoing area of life/work → 40-areas/<name>/.
   • Pure reference (book, paper, person, concept) → 50-resources/.
   • Just a link → 60-bookmarks/.
   • Unclear → 10-inbox/ with a capture filename; don't force a guess.
2. Write the note with full frontmatter per conventions. Rename imported files to kebab-case.
3. If it's source material worth synthesizing, put the untouched original in raw/ and write the synthesis as a separate wiki/ note that links back to it.
4. Add at least 2 internal links where natural. Link to hub notes, not random leaves.
5. Append a row to 00-meta/log.md (op: ingest). If a new hub, area, or collection appeared, update 00-meta/index.md.

Process inbox — "process the inbox," "clean up the inbox"

1. List 10-inbox/ contents, group items into small semantic batches (3–7 items).
2. For each batch, propose destinations to the owner before moving. Preflight every move: source exists, destination doesn't, parent directory is intentional.
3. Moved notes get their frontmatter completed and links added; they stop being type: inbox.
4. If an item spawns a new project or area, scaffold it from 00-meta/templates/.
5. Finish with a log append and index update.

Query — "where is…," "what do I know about…," "summarize my notes on…"

1. Check 00-meta/index.md first — it points to hubs.
2. Then search filenames, then note content.
3. Answer from vault content and cite the notes you drew from as links. If the vault has nothing, say so plainly — don't pad from general knowledge without flagging it.
4. Substantial research sessions get a query row in the log.

Lint — "lint the vault," or piggybacked on other work

Mechanical compliance pass. Check and fix (with owner approval for anything destructive):

• Notes missing frontmatter or required fields; updated: older than real modification.
• Naming violations (dates, case, tag format).
• Broken internal links; evergreen notes with fewer than 2 outbound links.
• 00-meta/index.md entries pointing at moved/dead paths.

Log op: lint.

Audit — "audit the vault" (periodic, deeper)

• Inbox items older than ~2 weeks — nag the owner to process.
• Projects with no activity for ~2 months — propose status: someday or a move to 90-archive/.
• Areas or resource hubs that exist on disk but not in the index.
• raw/ files nothing links to — propose synthesis or archival.

Report findings to the owner; act only on what they approve. Log op: audit.

Standing rules

• raw/ is read-only, forever. Deletion anywhere requires explicit owner confirmation.
• Never link into 10-inbox/ from elsewhere.
• Every write ends with the frontmatter check; every session that changed the vault ends with the log append.
• When a project folder is involved, read that project's AGENTS.md before touching it.