Verification Before Completion

Run explicit verification commands and collect fresh evidence like exit codes to verify software builds and test runs. This protocol ensures outcomes are confirmed with a transparent report detailing actual outputs and failures before declaring work finished.

Evidence-first quality assurance enforces a 5-step verification process: identify, run, read, verify, and claim. It solves inflated metrics by requiring transparent reporting of actual status with verifiable evidence in every completion claim.

Automate validation for code reviews and QA tasks by applying a verification protocol across reviews, builds, and tests. Instruct the agent to run the full workflow and report the validated status based on actual exit codes and outputs before completion.

Yes, the verification protocol works for documentation approvals where verification is mandatory. It applies the same 5-step process to generate a transparent report detailing outputs and any failures to determine the actual status before completion.

Claiming completion without verification leads to unreliable outcomes because it inflates metrics with unconfirmed results. Enforcing an evidence-first approach ensures transparent reporting of actual status with verifiable evidence in every completion claim.

Generate transparent reports for test automation by running explicit verification commands and collecting fresh evidence. This protocol details outputs, exit codes, and any failures to determine the actual validated status before claiming completion.