ledger-auditlisted

# ledger-audit A retrospective pass over a project that already exists, which is every project, the first time this is installed. Without it the ledger only ever knows about work done after installation, and starts from an empty file on a codebase with two years of decisions in it. **An audit is the one moment interrogation is welcome.** The user sat down for it. That makes a batch of questions acceptable here and nowhere else, and it is the only place in this family where that is true. Everything in `/ledger` exists to keep questions rare; that budget does not apply once someone has explicitly asked to be audited. ```bash for p in ~/.claude/skills/decision-ledger/bin/ledger \ ~/.claude/skills/ledger-audit/bin/ledger \ .claude/skills/ledger-audit/bin/ledger \ .agents/skills/ledger-audit/bin/ledger; do [ -x "$p" ] && LEDGER="$p" && break done $LEDGER audit --depth 5 ``` The list covers both ways this can be installed: `install.sh`, which lays down the whole repo, and a skills registry, which copies this directory alone. The command prepares the material: inherited conventions first, then previously undefended decisions. **It writes nothing.** Reading the codebase, asking the questions and recording the answers is your job. ## Rules **Ground every question in this codebase.** This is what separates an audit from the quiz this whole project exists to avoid. > Your `users` table has a soft-delete column. Why not a real delete? is unanswerabl