verification-before-completionlisted

# Verification Before Completion ## When to use Run this before claiming any work is done, fixed, passing, building, or complete. It is the evidence gate: name the claim, look up what evidence that kind of claim requires, and check that you hold that evidence from the current turn — not from before your last edit. Use it when you are about to say "tests pass", "the bug is fixed", "it builds", "the schema validates", "I didn't touch that file", or any status report a human would act on. Works in any project, under any build process — it requires no spec tree and no Cortex module. If you are about to write a completion summary, you are in scope. ## The Iron Law NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE Violating the letter of this law is violating the spirit. If you find yourself constructing a reading under which this does not apply to your case, that construction is the violation. "Fresh" means: produced in the current turn, **after** your most recent change. Evidence from before the last edit describes a state that no longer exists. Hardening mechanisms per `skills/_conventions/hardening.md`. ## The gate Run this before the claim leaves your mouth — not after, not "at the end". 1. **Name the claim.** Write the sentence you are about to say. "All tests pass." "The bug is fixed." "Nothing else changed." 2. **Look it up** in the claim→evidence table below. If your claim is not listed, find the nearest row; the principle generalises. 3. **Check fre