Verification Before Completion

Claiming work is complete without verification is unreliable. Always prove the claim with fresh evidence.

Why this matters: Unverified "done" breaks trust and wastes time—someone has to find the failing test or the broken build. Taking thirty seconds to run the command and read the output keeps the team (and the user) from chasing ghosts. It’s not bureaucracy; it’s the cheapest way to stay honest.

Core Principle

Evidence before claims, always. If you have not run the verification command in this session and read its output, you cannot claim the result.

Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

When to Activate