# Anti-Rationalization Checklist（evolution-engine）

| Rationalization | Reality |
|---|---|
| "One feedback entry is enough to propose a change" | A single entry is an anecdote, not a signal. The 3-occurrence threshold exists to prevent bloating rules with one-off issues. |
| "This pattern is clear, no need to cross-reference task-history" | Clear patterns can still be false correlations. Always check task-history to validate the signal. |
| "A low score on one dimension is enough to propose optimization" | Check the denominator: a skill used 100 times at 80% is fine. A skill used 5 times at 60% is noise. |
| "Just generate the proposal directly, no need for WebSearch" | When proposing new rules or Skills, existing best practices may already solve the problem. Search before inventing. |
| "Skip the Verify-by section, the fix is obvious" | A proposal without verification can't be confirmed as fixed. Every proposal needs an observable, time-bounded Verify-by. |
| "This proposal is ready even without the RED observation" | RED observation is the "why". Without it, the GREEN change has no rationale and can't be evaluated for correctness. |
