Verification Before Completion

Use before saying work is done, fixed, passing, or ready.

Iron Rule

No completion claim without fresh command evidence from this turn.

Verification Gate

Before any success claim:

1. Identify the exact command that proves the claim.
2. Run it now.
3. Read full output and exit code.
4. Confirm output supports the claim.
5. Only then report success, with evidence.

Required Evidence by Claim Type

• “Build passes” → successful bild <namespace>
• “Tests pass” → successful bild --test <namespace> or test command output
• “Typecheck passes” → successful typecheck.sh <file>
• “Bug fixed” → reproduction test now passes
• “Config change works” → output reflects intended config (not just 200/OK)

Red Flags

• “should work”
• “probably fixed”
• “looks good”
• reporting success based on stale output

If you see these, run verification again.

Response Pattern

Report:

• command run,
• key output,
• pass/fail status,
• any remaining risk.