verification-before-completion

To enforce verification evidence before claiming a deployment is complete, you must run a full verification sequence, inspect all outputs and failures, and attach verifiable results as evidence prior to declaring success.

The best way to prevent premature completion claims in code changes is to mandate fresh verification evidence, requiring you to identify the proving command, run it end-to-end, and review the full output before asserting success.

To capture and preserve test results for compliance audits, you must execute the proving command end-to-end, inspect the outputs, and attach the resulting logs and test results as verifiable evidence of the formal verification sequence.

Yes, this verification process applies to both pull requests and deployments, mandating a full verification sequence and evidence review across development tasks to guarantee verifiable completion before declaring success.

To verify quality assurance before marking a task done, you must identify the specific proving command, run it end-to-end, inspect the full output for failures, and attach those verifiable results as evidence of success.