verification-before-completion

Verification before completion prevents premature success statements by enforcing a process to identify a proving command, execute it fully, and interpret the output. It ensures claims are backed by fresh evidence during code reviews, PR approvals, and release readiness discussions.

Quality-assurance checks before finalizing a commit require identifying a proving command, running it in full, and verifying the results. This process guarantees that completion claims are supported by actual evidence rather than assumptions before reporting success.

The best way to back up completion claims with CI evidence is to run the full proving command, read and interpret the output, and verify the results. This guarantees that any reported success is backed by fresh, verifiable evidence.

You need to run proving commands fully and interpret their output to verify results before a release. This ensures that all completion claims are backed by fresh verification evidence, preventing dishonest or premature success statements during release readiness checks.

Stating completion without verification causes problems because claims lack fresh evidence. Without identifying and running a proving command to verify the output, code reviews risk accepting premature or dishonest success statements.

You can use this verification workflow across software projects where verification is required before reporting success. It applies whenever preparing to commit, create PRs, or finalize work, ensuring completion claims are always backed by fresh evidence.