verification-before-completion

To enforce verification before completion, you must execute a fresh verification command, inspect its output, and attach the resulting evidence to your PR. This ensures every success claim is backed by demonstrable logs and artifacts.

A quality gate for completion claims requires running fresh verification commands and reviewing their outputs before declaring a task done. It prevents unverified claims by enforcing evidence collection and status reporting.

You collect evidence for QA verification by running your verification workflow, capturing the command outputs and logs, and attaching those artifacts to your status report. This provides verifiable proof that all checks pass.

The best way to prevent unverified claims under PR pressure is to implement a strict verification gate. This requires parsing fresh verification command outputs and attaching evidence before any success status is reported.

No specific QA tools are required. The process applies to any scenario where you can execute fresh verification commands, parse their outputs, and attach the resulting logs as evidence to support your status claims.