verification-before-completion

# Execute → About to claim "done", "passing", "fixed", "complete"? → **Run the verification command first. Then claim.** 1. Identify: what command proves the claim? 2. Run: full command, fresh, complete 3. Read: output, exit code, failures 4. Verify: output confirms claim? → state claim WITH evidence. Doesn't? → state actual status. → Done when: exact command run, output confirms, residual risk stated, confidence graded. Non-trivial code changes → also report Complexity Delta and Complexity Governance Suggestion. Governance/retirement work → also close Repair Track + Retirement Track + Residual Risk. # Verification Before Completion ## Overview Claiming work is complete without verification is dishonesty, not efficiency. Evidence before claims, always. ## Red Flags - STOP - 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 run verification** ## When To Apply Before ANY success/completion claim, expression of satisfaction, commit, PR, task completion, or delegation. Applies to exact phrases, paraphrases, and implications. ## QA Closure Before any success claim, include the required evidence semantic slots. Natural prose, localized headings, or compact cards are all va...