vault-healthlisted

# Vault Health — Maintenance Workflow ## Mode Detection **Check the first argument:** - No argument → **interactive mode**: run all phases, ask before executing fixes. - Argument is `auto` → **auto mode**: run phases 1–3 only, stop before phase 4. No questions. No fixes. Write report and exit. Auto mode is designed for scheduled runs where no human is present. --- ## Phase 1 — Confidence Decay Safe to run in both modes. Decay is deterministic and reversible via git. 1. Read `_system/INDEX.md` for the full node list. 2. For each node: read frontmatter, calculate days since `verified_at`. 3. Apply decay: | Days since verified | Action | |---|---| | 91–180 | Reduce `confidence` by 0.1 (floor: 0.1) | | 181–365 | Reduce `confidence` by 0.2 (floor: 0.1) | | > 365 | Set `confidence` to 0.1, append `needs-review` to tags | | > 90 AND staleness_signal is triggered | Set `confidence` to 0.1 | 4. Update only the `confidence` field (and `tags` for >365 case). Touch nothing else. 5. Track: nodes scanned, nodes decayed, breakdown by type. **Skip:** `visibility: system` nodes, `verified_at: "Empty"` nodes, nodes created < 30 days ago. --- ## Phase 2 — Health Audit Collect findings only. Do not modify any node during this phase. 1. **Orphan Census** — zero edges AND zero `related` links. 2. **Contradiction Scan** — conflicting claims within the same namespace. 3. **Confidence Gaps** — `confidence` missing, 0.0, or high confidence on a triggered staleness signal. 4. **Stale Node