verification-before-completion

To prevent unverified completion claims, require fresh verification evidence from tests, linters, and builds before marking work as done. This ensures honesty and traceable verification by evaluating command outputs for truthfulness before reporting success.

Enforce evidence-driven reporting in code reviews by defining a verifiable checklist of commands to run and evaluating their outputs. This provides traceable quality and ensures success claims are reproducible and auditable before approving PRs.

Evidence-driven verification is the process of running tests, linters, and builds, then validating their outputs to confirm success before reporting completion. It specifies which commands to run, how to read outputs, and how to report results for auditability.

Yes, you can use automated verification checklists in CI pipelines to enforce evidence-driven reporting. By requiring fresh test and build outputs, you achieve traceable quality assurance and prevent unverified success claims in your software development workflow.

The best way to ensure reproducibility and auditability of success claims is to enforce evidence-driven verification. By specifying which commands to run and how to read their outputs, you guarantee that completion claims are backed by fresh, traceable verification evidence.