| name | vault-maintenance |
| description | Tactic for vault health upkeep — lint, orphan resolution, merge candidates, confidence updates. Minimum yield ≥1 issue resolved per invocation. |
| execution | tactic |
| used-by | ["campaign"] |
Vault Maintenance
Vault health upkeep. Called when CC judges the vault has accumulated enough entropy to warrant cleanup, or periodically between research phases.
Available SOPs
wiki-lint-fix — run lint checks, identify issues, optionally auto-fixwiki-search — find near-duplicate candidates for mergingwiki-graph-query — explore orphan neighborhoods for reconnectionwiki-add-edge — reconnect orphans to the graph
Guiding Principles
- Lint first. Start with vault_lint in report mode to assess current health.
- Triage by severity. Errors (broken links, missing frontmatter) before warnings (orphans, stale entries).
- Conservative auto-fix. Only auto-fix safe operations (duplicate edge removal, stale index pruning). Manual intervention for ambiguous cases.
- Merge, don't delete. Near-duplicate pages should be merged (consolidate content, redirect edges) rather than deleted.
- Confidence decay. Pages with evidence older than the research horizon may need confidence score updates.
Minimum Yield
≥1 issue resolved per invocation.
If vault_lint returns zero issues, report clean state and exit.
Execution Guidance
CC has full autonomy over:
- Which issues to address and in what order
- Whether to auto-fix or manually resolve
- How aggressively to merge near-duplicates
- When to update confidence scores
Typical flow (reference, not prescription):
- Run vault_lint (report mode) — assess issue landscape
- Categorize: auto-fixable vs manual
- Auto-fix safe issues (duplicate edges, stale index)
- For orphans: search for connection candidates, add edges
- For near-duplicates: merge content into canonical page, update edges
- Re-run vault_lint to confirm resolution
