Verification Before Completion

Core Principle: No completion claims without fresh verification evidence.

Unverified claims break trust and ship broken code: undefined functions that crash production, incomplete features missing requirements, lost time on rework after false completion. The cost of running one command is trivial compared to the cost of a wrong claim.

The Verification Gate

Before any claim of success, completion, or satisfaction:

1. IDENTIFY - What command proves this claim?
2. RUN - Execute the full verification command (fresh, complete)
3. READ - Check full output, exit code, failure counts
4. VERIFY - Does output confirm the claim?
   • NO - State actual status with evidence
   • YES - State claim WITH evidence from step 2-3

When This Applies