verification-before-completion

A verification gate prevents false completion claims by identifying the proving command, running it, and checking the exit status and complete output before allowing any success language in PR or commit communications.

Evidence-based verification requires running the specific testing or linting command and reading the complete output, including failure counts, before claiming a task is complete. It blocks success statements unless fresh verification ran in the same message.

To enforce quality assurance checks before a commit, use a verification gate that identifies the proving command, runs it fully, checks the exit status and output, and only then allows completion language in your commit readiness workflow.

Yes, the verification gate applies to common engineering tasks including linting, builds, regression cycles, and CI workflows. It ensures you do not rely on guesses or partial checks by requiring fresh verification evidence before any success statement.

Success statements are blocked during regression verification to provide anti-rationalization guardrails. This prevents dismissals like should work or agent said so unless the actual verification command ran and its complete output was checked in the same message.

No, the gate includes anti-rationalization guardrails that block success language and dismissals like just this once unless the full verification command ran and its complete output was verified in the same message.