verification-before-completion

To prevent premature completion claims in code changes, you must run a defined verification sequence producing fresh evidence, such as passing tests and builds, before declaring success.

Evidence-based completion for pull requests is a verification gate that requires capturing fresh outputs from lint, tests, and builds to ensure reproducible results before reporting success.

To run a verification gate before declaring a task finished, execute exact verification commands, evaluate the outputs, and attach the resulting evidence to your completion claim.

Yes, this verification approach works for documentation and builds by applying an explicit verification step to any code changes where fresh outputs are needed to confirm success.

Reporting results requires fresh verification evidence to guard against dishonest claims and ensure that completion declarations are backed by reproducible outputs from actual test and build executions.

The best way to enforce claim integrity during task completion is to define and execute verification commands, capture their outputs, and only publish results after confirming verifiable outcomes.