Vault Audit — Full 7-Phase Vault Health Check

• Architect — MANDATORY. Report ALL structural issues you find: overlapping areas, missing _index.md files, folders without corresponding MOCs, taxonomy drift, areas without templates, orphan folders with no purpose. The Architect is the only agent that can fix structural problems — you detect them, the Architect resolves them. Be specific: list the exact paths and what's wrong.
• Sorter — when you find misplaced notes that should be re-filed
• Connector — when you find clusters of orphan notes that should be linked but have no obvious connections yet
• Seeker — when you find notes with conflicting or duplicate information that need a content-level reconciliation
• Scribe — when notes are missing required frontmatter or are structurally malformed; ask Scribe to reformat them

Legacy cleanup

If the vault still has a Meta/agent-messages.md file from the old messaging system, rename it to Meta/agent-messages-DEPRECATED.md during maintenance. The new system uses dispatcher-driven orchestration — no shared message board.

Output format for suggestions

### Suggested next agent
- **Agent**: architect
- **Reason**: Found 3 areas without _index.md and 2 orphan folders
- **Context**: 02-Areas/Health/ missing _index.md. 02-Areas/Finance/ missing _index.md. 03-Resources/Old Projects/ and 03-Resources/Archive/ have no purpose in vault-structure.md.

For the orchestration protocol, see references/agent-orchestration.md in the repo or the equivalent runtime copy. For the agent registry, see references/agents-registry.md in the repo or the equivalent runtime copy.

When to suggest a new agent

If you detect that the user needs functionality that NO existing agent provides, include a ### Suggested new agent section in your output. The active runtime wrapper or operator can route this to the Architect or a custom-agent workflow.

When to signal this:

• The user repeatedly asks for something outside any agent's capabilities
• The task requires a specialized workflow that none of the current agents handle
• The user explicitly says they wish an agent existed for a specific purpose

Output format:

### Suggested new agent
- **Need**: {what capability is missing}
- **Reason**: {why no existing agent can handle this}
- **Suggested role**: {brief description of what the new agent would do}

Do NOT suggest a new agent when:

• An existing agent can handle the task (even imperfectly)
• The user is asking something outside the vault's scope entirely
• The task is a one-off that does not warrant a dedicated agent

Full Audit Workflow

Phase 1: Structural Scan

Scan the entire vault directory structure:

1. Verify folder hierarchy matches the canonical structure in Meta/vault-structure.md
2. Detect orphan folders — empty directories or folders not in the expected structure
3. Find misplaced files — notes in the wrong location based on their type frontmatter
4. Check for files outside the structure — anything in the vault root that should be in a folder

Report findings:

Vault Structure

Folders compliant: {{N}}/{{N}}
Empty folders: {{list}}
Misplaced files: {{N}} notes found in wrong location

Phase 2: Duplicate Detection

Search for duplicate or near-duplicate content:

1. Exact filename matches — files with identical names in different folders
2. "(updated)" or "(copy)" variants — files like Note (updated).md, Note 2.md, Note (1).md
3. Similar content — notes with >70% content overlap based on a quick comparison
4. Conflicting versions — Obsidian sync conflicts (e.g., Note (conflict).md)

For each duplicate found:

1. Read both versions completely
2. Identify which is more recent/complete (check date, updated, file modification time)
3. Present a comparison to the user:

Duplicate found:

A: "Project Plan.md" (01-Projects/) — modified 2026-03-10, 45 lines
B: "Project Plan (updated).md" (01-Projects/) — modified 2026-03-18, 62 lines

Analysis: B is more recent and contains all of A's content + 17 new lines.
Recommendation: Keep B, rename to "Project Plan.md", archive A.

Ask the user for confirmation before merging or deleting.

Phase 3: Link Integrity

Audit all wikilinks in the vault:

1. Broken links — [[Note Title]] that point to non-existent notes
2. Orphan notes — notes with zero incoming links (not referenced by anything)
3. Incorrect paths — [[05-People/Marco]] when the file is actually [[05-People/Marco Rossi]]
4. Alias inconsistencies — same person/concept linked differently across notes

For broken links:

• If the target note was moved, update the link
• If the target note was deleted, ask the user
• If it's a typo, fix it

For orphan notes:

• Check if they should be linked from a MOC
• Suggest connections based on content/tags

Phase 4: Frontmatter Audit

Check YAML frontmatter consistency:

1. Missing required fields — every note should have at minimum: type, date, tags, status
2. Invalid values — dates in wrong format, unknown types, malformed tags
3. Tag consistency — check against Meta/tag-taxonomy.md, flag unknown tags
4. Status hygiene — notes still marked status: inbox but not in Inbox folder

Fix automatically:

• Date format normalization (all to YYYY-MM-DD)
• Tag format normalization (lowercase, hyphenated)
• Add missing status field based on file location

Ask before fixing:

• Missing type field (need user input)
• Unknown tags (add to taxonomy or correct?)

Phase 5: MOC Review

Audit all Map of Content files:

1. Completeness — every filed note should be reachable from at least one MOC
2. Broken MOC links — links in MOCs pointing to moved/deleted notes
3. Stale MOCs — MOCs not updated in >30 days with new notes available
4. Missing MOCs — clusters of 3+ notes on the same topic without a MOC

Phase 6: Cross-Agent Integration

Pull insights from other agents' domains:

1. Check Meta/agent-log.md for recent activity from all agents
2. If legacy Meta/agent-messages.md exists, rename to Meta/agent-messages-DEPRECATED.md
3. Cross-reference findings — e.g., if the Connector flagged orphan notes, include them in the link integrity report
4. Summarize inter-agent activity in the health report

Phase 7: Health Report

Generate a comprehensive vault health report:

---