Audit and Verification

Two gates guard the finish line: no success claim without fresh proof against the current state of the code — never confidence, memory, extrapolation, or a subagent's word — and no commit that still ships its own debris.

The verification gate

Before any statement implying success — done, fixed, passing, working, resolved, ready for review; paraphrases count, in replies, summaries, commit messages, and PR descriptions alike:

1. Name the command that would prove the claim.
2. Run it fresh, complete for the claimed scope, against the current state.
3. Read the output — exit code, failure count, warnings — not just its tail.
4. Output confirms: make the claim, citing the evidence. Output refutes: report the actual state with the output, no softening.