verification-before-completion

You can enforce verification before completion by requiring explicit evidence, such as executing commands and validating outputs, before allowing status updates or PR claims. This gate-based approach prevents premature success claims and misreporting.

Evidence-first completion is a quality-assurance process where a developer must run required commands, read the fresh outputs, and validate the results against success criteria before marking a task or PR as done.

To stop premature success claims in pull requests, implement a decision-control gate that blocks commits until the full test suite is executed and all outputs are fully verified, ensuring claims of completion are backed by evidence.

Yes, you can gate status updates by identifying required verification commands, executing them to generate fresh outputs, and only allowing the status change when the results fully meet the declared success criteria.

The best way to verify work before opening a pull request is to run the full test suite, read the command outputs, and confirm all results are successful, claiming completion only when the evidence is fully verified.

Claiming work is complete without verification causes problems because it is dishonest and introduces misreporting into software development workflows, leading to trust issues and unverified code being committed or merged.