verify-before-done

# Verification Before Completion ## Overview Claiming work is complete without verification is dishonesty, not efficiency. **Core principle:** Evidence before claims, always. ## The Iron Law ``` NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE ``` If you haven't run the verification command in THIS run, you cannot claim it passes. A previous run, "should pass", or "looks correct" is not evidence. ## The Gate Function Before claiming any status or moving any task forward: 1. IDENTIFY — what command proves this claim? 2. RUN — execute the full command, fresh and complete. 3. READ — the full output: exit code, failure count, warnings. 4. VERIFY — does the output actually confirm the claim? If no: state the real status with evidence. 5. ONLY THEN — make the claim, with the evidence. Skipping any step is lying, not verifying. ## What Each Claim Requires | Claim | Requires | Not sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures | Previous run, "should pass" | | Build succeeds | Build command: exit 0 | Linter passing, logs look fine | | Bug fixed | Re-run the original symptom: passes | Code changed, assumed fixed | | AC met | Line-by-line check of every acceptance criterion | Tests passing | Tests passing is NOT the same as requirements met — re-read every acceptance criterion and confirm each one is actually satisfied. ## Board Handoff When the checks pass and every AC is confirmed, your closing action is your r...