verification-before-completionlisted

# Verification Before Completion > **NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE** ## Core Protocol Evidence before claims, always. If you haven't run the verification command in this message, you cannot claim it passes. ``` BEFORE any completion claim: 1. IDENTIFY: What verification command proves this claim? 2. RUN: Execute the FULL command (fresh, complete) 3. READ: Full output, check exit code, count failures 4. VERIFY: Does output confirm the claim? - NO → State actual status with evidence - YES → State claim WITH evidence 5. ONLY THEN: Make the claim ``` ### Command Selection When multiple verification options exist (mono-repo, multiple suites): - Run the **most specific** command that covers the changed code - When uncertain, run the **broadest** command (full test suite > single file) - Lint ≠ build ≠ test — each verifies different claims ### Evidence Format ``` ✅ Ran: npm test Exit: 0 Result: 47 passed, 0 failed "All tests pass." ❌ "Tests should pass now" (no command output) ``` ## Verification Requirements by Claim Type | Claim | Required Evidence | Insufficient | |-------|-------------------|--------------| | Tests pass | Test output: 0 failures | Previous run, "should pass" | | Linter clean | Linter output: 0 errors | Partial check, extrapolation | | Build succeeds | Build exit code: 0 | Linter passing | | Bug fixed | Original symptom test passes | Code changed | | Regression test | Red-green cycle verified | Single green | |