verification-before-completion

You prevent premature task completion claims by requiring fresh verification command outputs before approving any task. This enforces an evidence-before-claims rule, stopping rationalizations and ensuring actual process integrity before finalizing project workflows.

The evidence before claims principle dictates that no claims of fixing or passing are valid without fresh verification command outputs. It eliminates rationalizations by enforcing strict verification execution before any task completion status is officially recognized.

You enforce verification by mandating the execution of verification commands and evaluating their output before allowing any completion claims. Using a common failures checklist also helps identify and avoid typical shortcuts and rationalizations during the process.

Your task completion verification process fails due to common shortcuts and rationalizations that bypass running verification commands. Ignoring actual command outputs leads to unsupported success claims, directly violating the required evidence before claims principle.

Yes, you must run verification commands for every task completion claim. The system enforces that all claims of passing, fixing, or finishing are supported by fresh verification outputs, eliminating rationalizations and ensuring true process integrity.