verification-before-completion

To prevent premature completion claims, you must enforce a strict verification protocol that mandates running specific test commands and analyzing their output and exit codes before allowing any success assertions. This ensures evidence always precedes claims.

The best way to verify system health is to run automated agent system diagnostics, including health checks, full diagnostics, and vault analytics, alongside the specific failed test to ensure no new issues were introduced before asserting a bug fix.

You can enforce mandatory verification in automated workflows by implementing a protocol that requires fresh execution of verification commands and analysis of their output, ensuring accuracy and preventing the propagation of errors before making satisfaction claims.

Agents declare success prematurely when a strict verification protocol is missing, allowing assertions without evidence; enforcing mandatory command execution and system health diagnostics prevents these premature declarations of task completion.

Yes, you need to run system diagnostics to ensure evidence before assertions because the protocol mandates automated health checks and vault analytics to verify work completion and system status before making any claims of success.

Yes, you can use verification checks to stop premature declarations by mandating that all claims of work completion or passing statuses are backed by freshly executed verification commands and their analyzed output before any assertion is made.