verification-before-completion

Enforcing verification checks before completion requires running proving commands and confirming their outputs to produce fresh evidence. You identify the appropriate command, execute it fully, read the results, and verify the outcome before stating success.

Release governance requires fresh evidence for claims to prevent stating completion without verification. You need this process whenever marking work as complete, fixed, or ready for PRs, ensuring evidence-backed status changes.

To verify completion before merging, run the specific verification command to generate fresh output, confirm the results match expectations, and attach this evidence to your PR. This enforces a disciplined step-by-step quality assurance workflow.

Yes, you can apply this verification process to any release governance workflow. It operates independently without dependencies, requiring only that you execute and review verification commands before changing task status to complete or fixed.

The best way to prevent false completion claims is enforcing a strict audit workflow. Identify the proving command, run it fully, read the results, verify the outcome, and only then state success to ensure evidence-backed claims.

Stating success without running verification commands breaks the disciplined audit process. You must produce fresh evidence by executing the proving command and confirming the output before any status change to complete or ready for PRs.