verification-before-completion

To prevent false completion claims, you must enforce a verification workflow that runs fresh verification commands and reports concrete evidence before declaring success. This ensures status updates and PR approvals are backed by validated outputs.

Evidence-based verification for pull requests is a governance process that checks and reports fresh command outputs to support completion claims. It requires validating results and attaching them as evidence before any PR approval is granted.

You can enforce task verification before a release by running the full verification suite and reviewing the resulting outputs. You should only claim completion after validating this fresh evidence to ensure quality assurance.

Yes, the verification process integrates with existing quality assurance workflows by intercepting status updates. It requires the tool or agent to run verification commands, validate outputs, and report concrete results before asserting success in any workflow.

Agents claim task completion without verification when a formal evidence-based confirmation step is missing. Enforcing a required verification step preempts this by making the agent run validation commands and review fresh outputs before publicizing success.