verification-before-completion

You can enforce fresh verification evidence before completion claims by running verification commands, inspecting outputs, and documenting explicit pass or fail signals for traceable status across PRs or release gates.

Evidence-based verification for CI pipelines requires running fresh verification commands and documenting their outputs before making any success statements, preventing unverified completion claims and reducing release risk.

To add reproducible checks to commit and release gates, integrate verification commands that produce auditable status with explicit pass or fail signals, ensuring completion is only claimed with fresh evidence.

Yes, it integrates with local verification commands and CI pipelines by requiring the execution of fresh checks and inspecting outputs to produce auditable, traceable status before any completion claim.

Requiring fresh verification evidence before marking a task complete prevents dishonest and risky unverified claims, reducing the chance of releasing incomplete work by ensuring success statements are backed by verifiable outputs.

The limitation is that completion is strictly blocked unless fresh verification commands are executed and documented, meaning any success statement without explicit passing evidence will be prevented.