verification-before-completion

Verification before completion requires executing verification commands, analyzing their outputs, and documenting fresh evidence before marking any task as done. This gate process ensures claims are backed by verifiable outputs.

To verify test results before merging a PR, run the full verification command, review the output for failures, and only claim success when evidence confirms it. This ensures every claim is backed by fresh outputs.

The evidence-based completion process is a repeatable gate: IDENTIFY what needs checking, RUN the command, READ the output, VERIFY the results, and ONLY THEN claim success. This prevents misleading stakeholders with unverified claims.

Yes, this verification gate applies to deployment workflows where claims must be backed by verifiable outputs. It requires executing verification commands and analyzing outputs to satisfy compliance requirements before declaring success.

The best way to enforce compliance checks is applying a disciplined verification gate that requires fresh evidence before declaring success. This prevents claiming work as complete without verifiable verification, ensuring governance and quality.