verification-before-completion

To prevent premature completion claims, enforce a verification gate that requires running the test or build command and reviewing fresh outputs before asserting success. This structured checklist ensures you identify the command, run it fully, read the results, and only then claim completion.

Evidence-based verification is the practice of producing traceable command outputs to validate tests, linting, builds, and PR readiness before declaring a task complete. It solves the problem of dishonest reporting by enforcing fresh evidence over unsupported assertions.

To validate PR readiness, run the full verification sequence for your tests and linting, then attach the latest command outputs to your PR. This produces traceable, audit-friendly evidence that supports your completion status and confirms no failures were left undetected.

Yes, software verification can work without external dependencies because it operates as a structured gate within your existing workflow. You simply identify your specific validation command, run it fully, and read the outputs to verify results before claiming success.

The best way to enforce a verification gate is to follow a structured checklist: identify the verification command, run it fully, read and verify the outputs, and only then claim success. This ensures accuracy and prevents undetected failures in software development.