verification-before-completion

To enforce fresh evidence before completion, run a designated verification command in the current execution context to capture the exit code and output. This ensures all final success claims are backed by freshly produced build, test, or lint evidence.

Evidence-backed completion is a governance practice that requires running a verification command to produce fresh execution context output before declaring a task done. It standardizes evidence format by capturing the command, exit code, key output, and conclusion.

To document partial verification, explicitly state the limitations encountered during the verification command execution and list the next verification steps required. This clearly indicates that full evidence-backed completion was not achieved in the current run.

Yes, you can run verification commands across build, test, lint, and migration workflows. The process executes the validating command completely, captures relevant output, and reports results with evidence regardless of the specific software project workflow.

The best way to standardize quality-assurance evidence is to require a structured format capturing the validating command, exit code, key output, and final conclusion. This governance approach ensures consistent evidence production for all completion claims.

Completion claims fail without fresh verification output because the governance process requires evidence produced by a command run in the current execution context. Without capturing the exit code and relevant output, the success claim lacks the necessary validation evidence.