verification-before-completion

Evidence-based work completion requires running fresh test suites and build commands to verify code integrity before making any success assertions. This protocol prevents claiming work is finished without actual proof by mandating strict verification gatekeeping.

Preventing rationalized skipped verification involves applying a framework that counters excuses like confidence or fatigue. The protocol mandates identifying, running, and reading verification command outputs before declaring a task complete, ensuring strict adherence to quality assurance gates.

Verification gatekeeping works by requiring fresh execution of test and build commands before any status claims. It enforces a strict process of identifying verification commands, running them, and verifying their output to confirm the codebase truly passes all requirements.

No specific testing frameworks are required to enforce work completion verification. The protocol applies to any software development workflow where code integrity is critical, relying on running your existing test suites and build commands rather than introducing new dependencies.

Verification before completion should be applied whenever marking a task as done or submitting a pull request. It is necessary in software development workflows where accurate status reporting and code integrity are critical, ensuring all success claims are backed by verifiable evidence.