verification-before-completion

To prevent premature completion claims, enforce a verification-before-completion policy that requires fresh evidence from test runs and builds before marking work as done. This approach gates code merges by identifying the command, running full verification, and inspecting outputs.

A verification gate is a deterministic, repeatable checkpoint that requires running verification commands and reading their outputs before a PR can be marked complete. It guards against unverified success by enforcing evidence collection during PR reviews.

You can enforce verifiable evidence before merging code by applying a verification gate that runs full verification commands, reads the outputs, verifies the results, and reports the status before allowing a merge or completion claim.

Yes, verification gates work across software development workflows including code changes, builds, tests, and PR reviews. They apply a repeatable, auditable checkpoint to ensure integrity before any claim of completion is accepted.

Marking work as complete without verification leads to unverified success claims, risking code integrity. A verification-before-completion policy solves this by requiring fresh verification evidence from deterministic command outputs before any completion assertion.