verification-before-completion

To enforce verification before completion, you must execute verification commands like tests, builds, lint, or type checks and attach fresh evidence of the results. This prevents premature success claims by gating the completion status on actual command outputs.

A verification gate in software governance is a formal checkpoint requiring fresh evidence from actual verification commands before task completion is declared. It ensures claims of done work are backed by executed tests, builds, or lint results to prevent hidden defects.

Prevent premature success claims by requiring fresh evidence such as logs, exit codes, and artifacts from verification commands. Gating task completion on these visible results ensures stakeholders are not misled by unverified work passing as complete.

Yes, you can gate a PR merge or deployment by requiring successful execution of verification commands with visible results. This ensures that fresh evidence from tests, builds, or lint checks is attached before the work is marked complete.

Verification before completion applies across software development, data tasks, and operational work. It requires executing verification steps and attaching fresh evidence like exit codes or logs before marking any work as done, ensuring accuracy across domains.

The primary limitation is that fresh evidence requires actually executing verification commands like tests or builds. If the environment cannot run these checks or generate artifacts and exit codes, the completion gate cannot be satisfied.