verification-before-completion

To enforce verification before completion, run a full verification suite and validate command outputs and exit codes. Only after gathering this evidence should you update task status or claim PR completion.

Evidence-first reporting requires attaching structured verification results and command outputs to task handoffs or pull requests. This prevents unverified code changes from being reported as complete by demanding proof of successful checks.

You validate workflow outputs by executing verification commands and examining their exit codes and results. Declaring a release successful requires reporting this validation evidence rather than assuming completion based on process completion alone.

Yes, this verification workflow applies to data pipelines and QA processes. It enforces running a full verification suite and checking outputs before any success statements, preventing unverified changes across software, data workflows, and QA.

The best way to prevent unverified changes is to enforce an evidence-first verification workflow. This requires running a full verification suite, checking exit codes, and reporting structured results before making any success claims.

Task handoffs require validation evidence to ensure rigorous verification before completion. This prevents unverified changes from being reported as complete by enforcing that command outputs and exit codes are checked prior to any status updates.