verification-before-completion

To enforce evidence-based verification before declaring a pull request complete, you must run the full proving command, review the output and exit code, and report results with fresh evidence. This process gate prevents unverified success claims.

The process gate for verifying claims with evidence is a rigorous workflow requiring you to identify a proving command, run it fully, read the output and exit code, and report results. It ensures accountability across development cycles.

To verify work results before creating a commit or closing a task, run the full verification command relevant to your project, capture fresh output, and report the result with explicit evidence. This confirms claims are verifiable.

Yes, you can use this verification workflow for release cycles and commits. It applies across development workflows where verification is essential, guiding you to identify the proving command, run it fully, and verify results before completion.

The best way to prevent unverified success claims in software engineering is to enforce a step-by-step verification gate. This requires running a proving command fully, reviewing outputs and exit codes, and reporting results with fresh evidence before completion.