verification-before-completion

Verify completion claims by executing full test, lint, and build commands to generate fresh evidence. Only signal task completion after interpreting command outputs, logs, and exit codes to validate the success of the results.

Running fresh builds and tests before confirming a pull request prevents premature confirmations by ensuring explicit evidence exists. This governance pattern validates that observed results match success criteria before issuing status updates.

The best way to prevent premature completion claims in a CI/CD pipeline is enforcing a governance pattern where verification commands execute and outputs are evaluated. Status updates are only issued after verifiable results are observed across commits.

Validate exit codes and command outputs by reading and interpreting logs from your verification sequence. You evaluate these results to prove success, ensuring explicit evidence is observed before signaling a release or completion.

Yes, you can enforce a governance pattern that blocks status updates without test evidence. The system requires running full verification sequences and evaluating results to ensure explicit evidence exists before allowing any completion signaling.

You should not use automated verification before completion if your workflow does not support executing fresh test, lint, and build commands. The system relies on evaluating command outputs and exit codes to validate claims across commits and releases.