verification-before-completion

Verification evidence is enforced by running fresh verification commands and evaluating their full output before claiming completion. This deterministic workflow ensures development tasks, PR reviews, and deployment gates are backed by concrete proof of success.

Code quality gating follows a 5-step process: IDENTIFY the required verification commands, RUN them freshly, READ the complete output, VERIFY the results meet expectations, and only THEN CLAIM completion status with explicit evidence.

Yes, verification gating applies directly to pull request reviews and release gates. It ensures completion claims are backed by fresh evidence from freshly executed verification commands, making it suitable for CI workflows and deployment gating.

Prevent false completion claims by enforcing a deterministic workflow that requires running fresh verification commands and reading their full output. Only after validating results can a completion status be claimed, ensuring quality assurance in CI pipelines.

Fresh verification command execution is required because completion claims must be backed by current evidence. Relying on previous results risks false positives, so the workflow mandates running commands anew and reading the full output before declaring success.

No external dependencies or CI tools are required. The workflow operates as a standalone 5-step process—IDENTIFY, RUN, READ, VERIFY, CLAIM—governing completion status through fresh command execution and output validation in any development environment.