verification-before-completion

If you claim work is fixed without running verification commands, you violate the strict protocol that combats inefficiency and unreliability. The process mandates that no assertions of completion, fixed, or passing statuses can be made without concrete evidence from command outputs.

To enforce running tests before claiming code completion, you need a strict verification protocol that requires executing specific commands and reviewing their output as evidence before any success assertions are made. This prevents premature declarations of work being fixed or passing.

Evidence-based verification for bug fixes and code commits is a protocol requiring concrete proof, such as passing test suite output, before asserting a task is complete. It combats unreliability by ensuring no success claims are made without running verification commands.

You can prevent premature status updates by implementing a mandatory verification process that requires reviewing command outputs first. This ensures developers cannot claim work is passing or complete without presenting concrete evidence from their test suite runs.

Yes, this verification protocol applies to all stages of task completion, including code commits, pull requests, and status updates. It requires running verification commands and reviewing their output before asserting success across every phase of the workflow.

The best way to verify work completion before a pull request is to run the test suite, confirm zero failures, and present the test output as evidence. This evidence-based approach guarantees assertions of success are backed by concrete proof.