evidence-before-claimslisted

# Evidence-Before-Claims ## Overview **Core principle:** You may not claim something works until you have run the proving command **in this message** and read its output. Evidence first, claim second — always. "Should work" is not a status; it's a hope. ## The Iron Law ``` NO COMPLETION CLAIM WITHOUT FRESH VERIFICATION EVIDENCE ``` Fresh means *now*, in this turn — not "I ran it earlier," not "it passed last time." Code changed since then, or you wouldn't be claiming anything. A prior green run does not certify the current tree. ## The Gate Before any success claim, run this gate: 1. **IDENTIFY** the command that would *prove* the claim (the build, the test, the actual run that exercises the change — not a proxy). 2. **SCOPE it to the change's blast radius** — the set of behavior this edit could plausibly break. Not "the one test I wrote"; not "everything, always." See below. 3. **RUN it fresh, at that scope, in full.** No `--fast`, no bailing after the first green line. 4. **READ the whole output and the exit code.** Errors hide in the middle; exit code is the verdict. 5. **VERIFY** it actually shows what you're about to claim — the *right* thing passed, not just *something*. 6. **THEN claim** — and say what you ran *and what you didn't*. If you can't run the proving command, you don't claim success; you say what you verified and what you didn't. ## Scope by Blast Radius Verification breadth is a judgment, not a reflex. Running everything for a typo-fix trai