verification-before-completion

To enforce verification before completion, you must identify the verification command, execute it fully, read its output and exit code, and only state the result with evidence. This prevents claiming work as complete without verification.

Build verification for a PR review requires running the full verification command, auditing the output for failures, and saving the verifiable evidence. You cannot approve the PR until all tests pass and outputs are reviewed.

Claiming work is complete without evidence introduces risk and misalignment because status certainty is not guaranteed. Enforcing a verification workflow requires fresh, verifiable results before any status updates in PRs, deployments, or handoffs.

Process governance for verification applies to code, documentation, and project management tasks. Any task requiring status certainty, such as deployment checks or PR reviews, must execute the verification command fully and review the output before completion.

The best way to verify quality control before a handoff is to follow a repeatable verification workflow: identify the command, run it fully, audit the output for failures, and only claim success with fresh, verifiable evidence.