verification-before-completion

Verifiable completion requires executing a proving command, capturing its full output, and reporting status with evidence. This enforces evidence-first verification by making reproducible outputs mandatory before any success claims or pull requests are approved.

Evidence-first verification is a governance process requiring fresh execution results before signing off on code reviews. It identifies the proving command, runs it fully, analyzes the output, and gates task completion behind reproducible verification outputs.

To gate deployments, identify the command that proves completion, execute it to completion, and analyze the results. Report the final status only with attached evidence, providing an auditable decision gate for QA teams validating deployments.

Yes, task sign-offs can be gated by requiring fresh verification evidence. This is applicable for developers validating feature completion before PRs and team leads signing off only after reviewing verifiable, reproducible results from the proving command.

Claims without verification evidence lack auditable proof of success and risk false completion reporting. Requiring a full verification command execution ensures honesty in status reporting and prevents unverified code from progressing through development workflows.

Yes, it works for quality assurance by providing a repeatable decision gate. QA teams can gate deployments by identifying the proving command, executing it fully, capturing the output, and reporting status only with verifiable evidence attached.