verification-before-completion

To enforce verification before completion, identify your project's verification command, execute it in a fresh run on a clean workspace, and attach the parsed output as evidence to your status update.

Evidence-based completion requires fresh verification data from a clean run before any success claim is made. It prevents silent failures by ensuring outcomes are backed by verifiable results rather than assumptions.

Prevent silent failures during code reviews by applying a repeatable verification process that runs the verification command on a clean workspace, parses outputs for success criteria, and reports verifiable results.

Yes, you can use this process for quality assurance by identifying your specific verification command, running it on a clean workspace, and reviewing the output against your success criteria before reporting completion.

The best way to verify completion claims is to formalize the process: identify the verification command, execute it in a fresh run, parse the outputs, and report verifiable results to ensure accuracy and honesty in status reports.

Deployment gates fail to catch silent failures when completion claims lack fresh evidence. Enforcing verification before completion requires running the verification command in a fresh environment and attaching the output as proof.