verification-before-completion

Evidence-based verification requires a strict protocol of identifying, running, and reading verification command outputs before making any task completion claims. This prevents unverified assertions by forcing validation checks as a prerequisite gatekeeping step.

Preventing rationalization requires a framework that stops common excuses for skipping verification, such as relying on assumptions or partial checks. It enforces accountability by mandating strict adherence to running verification commands for every success assertion.

To systematically verify build status before a pull request, identify the specific command that proves your work is finished, execute it, and read the output. This protocol ensures tests and linter checks are validated before proceeding.

Yes, this verification protocol applies directly to agent-based workflows and task management. It enforces rigorous evidence-based validation for any system where accuracy and reliability are required before proceeding with completion claims.

Running verification commands instead of relying on assumptions ensures all assertions of success are backed by verifiable evidence. This prevents the common pitfall of claiming work is finished without actual proof, maintaining strict quality assurance.