verification-before-completion

1# Verification Before Completion
2 
3## Overview
4 
5**Core principle:** Evidence before claims, always.
6 
7**Violating the letter of this rule is violating the spirit of this rule.**
8 
9## The Iron Law
10 
11```
12NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
13```
14 
15If you haven't run the verification command in this message, you cannot claim it passes.
16 
17## The Gate Function
18 
19```
20BEFORE claiming any status or expressing satisfaction:
21 
221. IDENTIFY: What command proves this claim?
232. RUN: Execute the FULL command (fresh, complete)
243. READ: Full output, check exit code, count failures
254. VERIFY: Does output confirm the claim?
26   - If NO: State actual status with evidence
27   - If YES: State claim WITH evidence
285. ONLY THEN: Make the claim
29 
30Skip any step = lying, not verifying
31```
32 
33## Common Failures
34 
35| Claim | Requires | Not Sufficient |
36|-------|----------|----------------|
37| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
38| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
39| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
40| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
41| Regression test works | Red-green cycle verified | Test passes once |
42| Agent completed | VCS diff shows changes | Agent reports "success" |
43| Requirements met | Line-by-line checklist | Tests passing |
44 
45## Red Flags - STOP
46 
47- Using "should", "probably", "seems to"
48…