verification-before-completion

To enforce verification before completing a pull request, require fresh verification commands and documented output as evidence. This prevents premature completion claims by ensuring success is confirmed through explicit, verifiable test results rather than assumptions.

Evidence-based completion in CI-CD pipelines is the practice of capturing fresh command outputs to confirm a task is done. It prevents broken builds by requiring documented verification steps before any success claim is accepted during releases or code reviews.

Prevent premature completion claims by mandating that developers run full verification suites and present the captured output. This enforces evidence-based completion, ensuring no task is marked done without explicit, verifiable proof of success.

Yes, enforcing code review verification works for release checks. The process applies universally across pull requests and releases, requiring fresh verification commands and documented evidence to confirm that all release criteria are met before completion.

Requiring fresh verification outputs is necessary because claiming work is complete without verified evidence leads to broken builds and eroded trust. Demanding explicit, documented proof ensures that success claims are backed by actual test results.

The best way to confirm task completion and avoid broken builds is to run the full verification suite, capture the outputs, and declare completion only with explicit evidence. This evidence-based approach ensures all claims are verified.