vaultwatchlisted

Set up and operate an AUDITED knowledge vault: a plain-markdown second brain whose claims are verified by two instruments — a no-network coherence audit (the vault against itself) and a world audit (the vault against the running reality it describes: HTTP endpoints, served files, git remotes, on-chain state). Use this whenever the user wants a knowledge base, second brain, vault, wiki, HANDOFF, project memory, or documentation system for a repo that OPERATES something — servers, deployments, published content, prices, wallets, APIs — and also whenever they complain that docs drift, lie, go stale, or that "the README is always wrong". Covers bootstrapping a new vault, retrofitting auditors onto an existing docs/ folder, and the session-close ritual (fix what the session made false, re-run the audits, commit). If the knowledge is pure reading notes with no world that can contradict them, a plain wiki is enough and this skill is overkill.
yvalenta/vaultwatch · ★ 0 · Data & Documents · score 69

Install: claude install-skill yvalenta/vaultwatch

# vaultwatch — the wiki that gets audited against reality A second brain for **operated systems**. The difference from a normal wiki: the vault is not something you read — it is something you **run**. Two scripts decide whether it can be trusted before every working session, and they exist because AI-maintained wikis compound lies exactly as well as they compound knowledge: two pages can agree perfectly about a world that already changed. This method comes from a real repo that accumulated 37 false claims across six review rounds — all with tests green — including a rotated credential that a forgotten file kept publicly serving while three auditors passed. Every rule below was paid for before it was written. ## Step 0 — Decide the mode - **Bootstrap**: no docs exist yet → create the full structure (Step 1), then the auditors (Steps 2–3). - **Retrofit**: a docs/ folder already exists → do NOT reorganize it in one heroic pass. Create `state/` and move the *live figures* there one at a time (each move is a chance to re-measure them), add the auditors, and let the rest migrate when it's touched. A big-bang migration writes new lies. Ask which the user wants only if the repo doesn't make it obvious. ## Step 1 — The structure ``` docs/ ├── HANDOFF.md the cold-start door ├── state/ what is true TODAY ├── laws/ method notes, each born from a paid error └── history/ what happened, so it stops repeating ``` **`state/` — assertion sites.** Every li