verification-before-completion

Preventing dishonest completion claims requires enforcing a verification gate that collects fresh evidence, such as command outputs and test results, before allowing any status change, PR approval, or task closure to be asserted.

A verification gate for task closure is a process guardrail that blocks success assertions until verifiable outputs and test results are collected and reviewed, ensuring rigor and traceability across development workflows.

To require verification evidence before approving a PR, run the full verification command, review the outputs, and attach the collected logs and test results to support the completion claim with traceable proof.

Yes, the verification process works without external dependencies, applying an advanced internal design to guide teams through explicit verification steps, evidence collection, and failure reporting across development workflows.

The best way to ensure traceability for quality assurance claims is to collect and store fresh verification evidence, including command outputs and logs, which directly supports status updates and task closures with rigor.

You should not use an automated verification gate when a task requires subjective review without verifiable outputs, as the process specifically enforces collecting command outputs and test results to back success assertions.