[Feature] Vault Index: Librarian-managed metadata registry with privacy firewall

[gnekt]

💬 Join the discussion: https://discord.gg/EUnQmABw8s

---

Problem

Currently agents have no centralized awareness of what's in the vault. Every search is a brute-force scan. There's also no way to mark notes as private (excluded from LLM processing).

Proposed Solution

The Librarian builds and maintains an indexed registry of all .md files in the vault.

Registry structure (e.g. Meta/vault-index.md or .json):

• File path
• Title
• Tags
• Area/folder
• Created date
• Last modified
• Summary (one-liner)
• Privacy flag (public / private)

Privacy firewall

• Notes flagged as private are never read, summarized, or processed by any agent
• Private notes appear in the index (path + title only) but their content is off-limits
• User can set privacy via frontmatter (private: true) or by folder convention (e.g. Private/)
• All agents MUST check the index before reading any file

Librarian responsibilities

• Full rebuild on demand ("rebuild the index")
• Incremental update during maintenance routines
• Flag inconsistencies (file exists but not indexed, indexed but deleted)

Tasks

• Define index schema (format: MD table vs JSON vs CSV)
• Implement privacy flag detection (frontmatter + folder convention)
• Update Librarian agent to build/maintain the index
• Update ALL agents to check privacy flag before reading files
• Add user commands: "mark this as private", "show private notes", "rebuild index"