verification-before-completion

To enforce verification before completion, apply a strict protocol requiring fresh execution evidence for all success assertions. This mandates independent validation of test results and system state prior to finalizing any work or pull request.

Evidence-based reporting ensures that work completion claims like passing tests or successful builds are tied directly to fresh execution logs. It prevents relying on assumptions by validating command outputs against expected success criteria.

To validate build logs and test results before a pull request, execute a mandatory verification gate. Run the full test suite and build process to confirm the output matches expected success criteria rather than assuming completion.

Yes, you can use this verification protocol for task handoffs in software development. It ensures technical accuracy by requiring independent validation of system state and fresh execution logs before any success assertion is made.

Claiming work is finished without proof causes quality assurance issues because it allows unverified code to progress. Requiring fresh execution evidence prevents this pitfall by ensuring all assertions of success are backed by verifiable output.