verification-before-completion

A verification gate enforces a structured validation process before completion claims by requiring fresh evidence from executed commands. It ensures tests pass and linting is clean before asserting success, preventing premature or dishonest status updates.

Evidence-first validation in CI requires executing verification steps, collecting outputs, and validating success criteria before asserting completion. This mechanism ensures every status update is backed by fresh, reviewed verification evidence.

Run a verification sequence before merging by identifying the proving command, executing it fully, reviewing the complete output, and verifying the results. Only after confirming tests and checks succeed should you proclaim completion and merge.

Gate-driven validation works without external dependencies, relying on an internal advanced reasoning process to identify, run, read, and verify outcomes. It provides a repeatable process for honest progress reporting without requiring specific component installations.

The best way to prevent premature completion claims in code review is enforcing a formal verification gate. This approach requires producing and verifying fresh evidence, such as passing tests and clean linting, prior to making any completion assertions.

You need a verification gate for quality assurance before commits, pull requests, or status changes. It is required when you must support honest progress reporting by ensuring fresh verification evidence is produced and validated prior to assertions.