verification-before-completion

Enforce a verification gate by requiring fresh evidence before completion claims. A structured run-read-verify workflow mandates executing a concrete verification command, reviewing the full output, and reporting evidence to satisfy release readiness checks.

Requiring fresh verification evidence means validating tasks, tests, or builds with current output before declaring completion. This process prevents deception by enforcing a concrete verification command and evidence-based reporting for auditability.

Verify test completion claims by applying an evidence-based reporting workflow. Guide teams through running a verification command, reviewing full output, and validating results before marking tasks done to satisfy governance requirements and improve trust.

Yes, you can apply this verification workflow to project tasks without external dependencies. It operates as an intermediate-level gating mechanism within project workflows, requiring only a concrete verification command and full-output review to validate completion.

The best way to prevent unverified code from passing the release process is enforcing a gating mechanism. Require running a verification command, reviewing full output, and gathering fresh evidence before allowing any completion or release readiness claims.

Claiming work as complete without verification causes governance issues because it bypasses evidence-based validation. This practice introduces dishonesty into the release process by skipping the required test verification and full-output review needed for auditability.