verification-before-completion

Topics in the source

• Verification Before Completion
• Overview
• The Iron Law
• The Gate Function
• Common Failures
• Red Flags - STOP
• Rationalization Prevention
• Key Patterns

Claiming work is complete without verification is dishonesty, not efficiency. Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule. If you haven't run the verification command in this message, you cannot claim it passes. | Claim | Requires | Not Sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures | Previous run, "should pass" | | Linter clean | Linter output: 0 errors | Partial check, extrapolation | | Build succeeds | Build command: exit 0 | Linter passing, logs look good | | Bug fixed | Test original symptom: passes | Code changed, assumed fixed | | Regression test works | Red-green cycle verified | Test passes once | | Agent completed | VCS diff shows changes | Agent reports "success" | | Requirements met | Line-by-line checklist | Tests passing | Using "should", "probably", "seems to" Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.) About to commit/push/PR without verification Trusting agent success reports Relying on partial verification Thinking "just this once" Tired and wanting work over ANY wording implying success without having

This is an excerpt. Refer to the complete source and its current requirements.