verification-before-completion

To prevent premature task completion claims, enforce a strict verification protocol requiring fresh execution of testing commands and analysis of their output before any assertion is made. This ensures all success claims are backed by verifiable evidence.

Evidence-based verification is a protocol enforcing the execution of verification commands and analysis of their actual output before asserting any task status. It prevents unsubstantiated claims by requiring fresh, verifiable proof for every completion statement.

You can enforce running test suites before claiming completion by applying a mandatory verification protocol. This requires identifying, running, and reading the relevant test suite output to confirm zero failures before stating that tests passed or code is complete.

Automated agents often claim success without verification due to common rationalizations and red flag behaviors. Enforcing a strict protocol that requires fresh execution of verification commands prevents these errors and maintains honesty in agentic operations.

Yes, verification before completion applies to all stages of work, from development to deployment. It enforces running verification commands and analyzing their output before any assertion is made, preventing premature success claims across the entire workflow.

Relying on assertions without fresh execution evidence leads to premature or unsubstantiated claims of task completion. It bypasses the required analysis of actual verification command output, risking errors and eroding trust in automated status reports.