verification-before-completion

To enforce verification before declaring a task complete, identify required commands, run them fully, read their output, and report the final status with fresh evidence. This structured workflow prevents premature success claims in software development.

Evidence-first validation requires fresh command outputs to substantiate success claims during code reviews or task claiming. It ensures that developers provide concrete proof of execution rather than assuming functionality without verification.

To prevent premature success claims during a sprint closeout, teams run a structured verification sequence before marking a task done. This ensures all command outputs match expected results, providing concrete evidence of completion.

The best way to verify code review results is by executing a structured workflow: identify the required verification commands, run them in full, read and interpret the output, and verify the results match expectations before reporting the final status.

Yes, evidence-first validation supports software development governance by enforcing verification before completion. It requires running verification commands and reporting final status with fresh evidence, preventing misrepresentation across development workflows.