verification-before-completion

To enforce verification before completion, run fresh verification commands and evaluate their outputs prior to any success claim. This validates tests, builds, and code reviews, ensuring evidence-based decisions and preventing premature completion statements.

Evidence-driven completion is the practice of capturing exit codes and failure counts as proof of state before marking a task complete. It requires inspecting outputs and producing explicit results to prevent misstatements about build or test status.

You validate tests and builds by running a verification sequence that checks the current task status. This workflow inspects outputs and captures explicit evidence, allowing you to decide whether to declare completion based on actual results.

No, this verification workflow does not require external dependencies or components. It functions as a standalone gate to enforce fresh verification commands and capture evidence directly within your existing development and automation environments.

A verification gate prevents premature completion claims by requiring fresh validation before asserting success. It captures exit codes and failure counts as proof of state, reducing misstatements and ensuring outputs are explicitly inspected.