verifying-completionlisted

# Verifying Completion A task is "done" only when its acceptance is observable — right now, in this turn, with output you read. Internal confidence, prior runs, and "it should work" are not evidence. ## The Iron Law ``` NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE ``` No completion claim is permitted unless the verification command ran in this message. Period. **Violating the letter of this rule is violating the spirit of this rule.** ## The Gate Function Before flipping a task to `done`, marking a sprint complete, approving a feature, or asserting any "X works" / "tests pass" / "fixed" / "ready" — run this gate: ``` 1. IDENTIFY: What command, in this exact moment, proves the claim? 2. RUN: Execute the FULL command from a clean state (fresh shell, fresh build). 3. READ: Read the FULL output. Capture exit code. Count failures. 4. VERIFY: Does the output literally confirm the claim? YES → state the claim WITH the evidence inline (last 10 lines + exit). NO → state actual status with the evidence; do NOT claim done. 5. ONLY THEN: Make the claim or flip the marker. Skipping any step = lying, not verifying. ``` ## Claim → Evidence Map | Claim | Required evidence | Insufficient | |---|---|---| | Tests pass | Test command output: `0 failed`, exit 0, run in this turn | "Last run was green" / "should pass" | | Fix works | Acceptance probe exit 0 with observable output proving wiring | "Code looks right" / "compile clean