verification-before-completion

Evidence-based completion requires running a full verification command and analyzing fresh outputs before asserting success. This prevents premature completion claims by attaching logs and results to support status claims in code reviews.

Evidence-based completion in software development is the practice of requiring fresh verification command outputs and logs before claiming work is finished. It enforces honesty, traceability, and accountability by attaching evidence to status claims.

Enforce code review verification with evidence capture by running full verification command sequences, reading the output, and attaching logs or results to your PR checklist. This auditable workflow ensures reproducibility and accountability before marking work complete.

Yes, you can use verification gates for sprint governance and PR checklists. The process requires executing fresh verification commands, validating outputs, and reporting status with evidence to ensure accountability and reproducible audit trails.

Running fresh verification commands before marking work complete prevents dishonest or unverified success claims. It ensures that completion status is backed by actual execution outputs, providing honest, traceable, and reproducible evidence of quality assurance.