verification-before-completion

To prevent false completion claims, enforce a verification gate requiring fresh evidence before asserting success. You must run verification commands fully, read the output results, and only declare task completion if the evidence proves success.

Evidence-based verification is a process requiring fresh proof of success before claiming completion. It enforces a command-by-command verification process for software builds, tests, and PRs to ensure outcomes are backed by actual output evidence.

Enforce step-by-step verification by running the full verification command, reviewing the output results, and attaching the evidence to your completion claims. Only declare success after verifying the results prove the task is complete.

Yes, this verification process applies directly to software builds, tests, code reviews, and PRs. It ensures evidence-based outcomes by applying a step-by-step verification gate before any success claim is accepted.

Requiring fresh verification evidence prevents dishonest or premature completion claims. It enforces a strict rule that success can only be declared after verification commands are run fully and their results prove success.

The best way to verify claims with evidence during quality assurance is to enforce a command-by-command verification process. Run commands fully, read the results, verify the outcomes, and only then declare completion.