The trap map

The trap map. After scoring, mark each miss with the trap that caught you:

• Misread clause → drill the operator-circling ritual.
• Dead variable → you predicted from vibes, not the table; drill state-table tracing.
• Order assumption → you simulated the example, not the code; drill two-key-trace (module 2's aliasing set).
• Mirror misapplication → you generalized a pattern the data doesn't support; drill boundary-case testing first.

The map matters because the four traps have different cures. "Tried hard, lost points" is not a diagnosis; "I assumed commuted mutations" is. Four misses from four different traps mean the issue is pacing (rushing); four from the same trap mean the issue is that mechanism — go re-run its module.