verification-before-completionlisted

# Verification Before Completion ## Overview Every completion claim requires fresh evidence. No exceptions. ## The Iron Law **NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.** "I believe it works" is not evidence. "The tests passed at 14:32" is evidence. If you have not run verification commands in this session and read their output, you have not verified. ## The Gate Function Before ANY claim that work is complete, execute this sequence: ``` 1. IDENTIFY - What claims am I about to make? 2. RUN - Execute the verification commands 3. READ - Read the actual output (not what I expect to see) 4. VERIFY - Does the output support each claim? 5. CLAIM - Only now state completion, citing evidence ``` **Every step is mandatory.** Skipping any step means the gate has not been passed. ### Step 1: IDENTIFY List every claim you are about to make. Be specific: ``` NOT: "It works" YES: "All 47 tests pass, the build succeeds, and the new endpoint returns 200" ``` Common implicit claims to surface: - "Tests pass" -- which tests? All of them? Just the new ones? - "Build succeeds" -- clean build or incremental? - "Bug is fixed" -- does the specific reproduction case now succeed? - "No regressions" -- have you run the full test suite, not just new tests? - "Ready to merge" -- does it pass lint, type checking, and formatting too? ### Step 2: RUN Execute the actual verification commands. Not from memory. Not from a previous run. ``` REQUIRED: Run the c