diff --git a/CLAUDE.md b/CLAUDE.md
index 9db7374..f1b8e6e 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -202,7 +202,10 @@ retail. Everything else is your call.
 
 - Continue to the next planned sub-step of a phase after the previous one
   lands clean — including immediately starting work on the next phase if the
-  current one is done
+  current one is done. **You pick what comes next** per the Milestone
+  discipline section — never present the user a menu like "should we do X
+  or Y?" or ask "what next?". Just choose and announce the choice in one
+  sentence. Work-order selection is Claude's job, not the user's.
 - Pick between two roughly equivalent implementations; justify the choice in
   the commit message
 - Refactor small amounts of surrounding code when genuinely needed to land a
@@ -545,6 +548,20 @@ collision + B.4 interaction. Demo target: walk through Holtburg without
 getting stuck, open the inn door, click an NPC, pick up an item.
 Estimated 4–6 weeks from 2026-05-12.
 
+**Work-order autonomy — the meta-rule.** You decide what to work on
+next, always. **The user does NOT pick between phases, milestones, or
+"what's next?" alternatives.** The milestone discipline + the
+per-milestone phase list + the roadmap IS the work order — drive it.
+Never ask the user "want me to start X or Y?" or present a menu of
+options. If two next steps are genuinely equivalent, state which one
+you picked and why in one sentence and start — don't ask. The user
+retains the right to redirect if they think you're wrong, but the
+default is **Claude drives, user reviews**. The user finds decision
+fatigue from constant work-order choices draining — that's literally
+what triggered the milestones doc on 2026-05-12. Honoring this rule is
+the single biggest morale lever. This is the meta-rule that makes the
+four below actually work.
+
 **The four motivation-keeping rules:**
 
 1. **One active milestone at a time.** Work that isn't on the critical