verification-before-completion

To enforce verification before claiming code completion, execute full verification commands, inspect outputs and exit codes, and only assert success after confirming the output supports the claim with evidence.

Evidence-first completion checking is a protocol that requires recording commands, outputs, and exit statuses to validate claims, preventing premature or dishonest conclusions about code development or release readiness.

To verify PR readiness, identify the command that proves the claim, execute it to obtain fresh output, inspect the complete output and exit code, and only then state the claim about success.

You need to gate releases with verification checks during code development, debugging, code reviews, and PR readiness scenarios to ensure any claim of completion is supported by fresh verification evidence.

The best way to prevent premature success claims in CI is to enforce a step-by-step verification protocol that requires running commands, reading complete outputs, and verifying exit codes before declaring completion.

Asserting completion without test output fails code reviews because the verification protocol requires fresh output and exit code analysis to validate claims, ensuring success is backed by verifiable results rather than assumptions.