verification-before-completion

To stop false completion claims, enforce verification protocols requiring agents to execute specific validation commands and review objective output evidence before any status update is communicated.

Evidence-based validation requires running specific verification commands to prove operational accuracy, ensuring every task completion claim is backed by objective output rather than assumptions or partial checks.

To verify a bug fix, mandate the execution of the specific regression test and confirm the output shows zero failures, preventing the agent from simply stating the code was changed.

False positives occur when agents rationalize skipping quality assurance and rely on assumptions instead of strict verification protocols that require independent review of actual command output.

Strict task validation applies directly to automated campaign management by requiring that any success status update is proven through the execution of specific validation commands and objective evidence review.

The best way to prevent rationalization is to implement a framework that identifies common excuses for skipping verification and mandates objective command output validation before allowing status updates.