Verification Before Completion

This is a discipline enforcer that stops you from saying "tests pass" or "bug fixed" without running the actual verification command in the same session. The core rule is simple: no fresh evidence, no completion claim. It includes a table of what counts as real verification versus what doesn't (spoiler: linter passing doesn't prove your build works), plus a list of red flags like using "should work" or trusting an agent's success report. Born from 24 documented failures where unverified claims broke trust and shipped broken code. Use it before any commit, PR, or completion statement. It's ruthlessly specific about the difference between confidence and proof.