verification-before-completion

To enforce verification evidence before a PR approval, you must identify the verification command, execute it fully, read the output, and validate it against acceptance criteria before declaring completion.

Verifying evidence before completion means precluding premature completion claims by capturing fresh verification outputs and reviewing them against required criteria before announcing success for a task sign-off.

Stop premature completion claims by requiring a full verification process: identify the command, run it, capture fresh results, read the outputs, and validate them before stating any success claim.

Yes, you can use it for quality assurance on software releases. It applies to releases, PR approvals, and task sign-offs where verification steps must be executed and outputs reviewed before declaring success.

The best way to attach fresh logs is to run the verification command fully on your current work, capture the fresh results, validate the output against acceptance criteria, and attach the logs before claiming completion.

You should validate output against acceptance criteria to ensure the verification process actually passed. Stating a completion claim without fresh verification evidence leads to premature and unverified success announcements.