prooflisted

# Proof ## Iron Law `NO ENGINEERING CLAIM WITHOUT A NAMED PROOF.` A named proof is a Proof Contract whose check would fail if the claim were false. ## When to Use Completion gate: - Before your next response would state or imply that work is done, fixed, ready to commit, ready for a PR, or passing. Do not settle for a vague `unproven`; name both the claim and the missing evidence. Main skill when the requested work is proof itself: - Adding or reviewing behavior-focused tests that prove a feature, bug fix, refactor, flaky test fix, or untested behavior. - Deciding what deserves coverage and which boundary the proof should enter through. - Converting an agreed spec, domain model, contract, or root-cause finding into Proof Contracts and executable checks. ## When NOT to Use - Pure formatting, typo fixes, or mechanical file moves with no behavior, data, or contract claim. - Mechanical refactors with no behavior surface (rename, file move, comment-only edits) verified by tooling or exact artifact inspection. Behavior-preserving refactors that change an observable boundary still need `proof`. - Investigating an unconfirmed bug or symptom where the cause is not yet established. Use `debugging` until there is a claim to assert, then return for the Proof Contract. - Reviewing changes for design, complexity, naming, or structure. Use `code-review`. Load `proof` only when the question is whether evidence is sufficient. - Load testing, profiling, or b