verification-before-completion

To enforce evidence-based verification before a pull request, you need an automated validation workflow that runs verification commands, parses test outputs, and attaches observable proof prior to marking any task as complete.

Evidence-based completion verification is a structured QA process requiring observable proof, such as passing test outputs and review records, to ensure accurate status reporting and reduce rework before claiming work is done.

You attach validation proof by running required verification commands, parsing their execution outputs, and recording the results as auditable evidence to support your status assertions for PR submission or task closure.

This verification process applies to both software development and content workflows, ensuring required validation steps are completed and verified before delivering work, submitting pull requests, or closing tasks.

You need guardrails for task validation to prevent inaccurate status reporting, enforce the execution of verification commands, and ensure deterministic auditable proof exists before any work is marked as complete.