diff --git a/docs/how-to/agent-change-process.md b/docs/how-to/agent-change-process.md
index 1cc09dd..60d5db0 100644
--- a/docs/how-to/agent-change-process.md
+++ b/docs/how-to/agent-change-process.md
@@ -42,7 +42,7 @@ A change with enough complexity or risk that a human should review it, but not s
 ### Process
 
 1. Run `mise run ai-docs` to load context
-2. **Search related docs** — read existing documentation, reference cards, and prior Mikado chains related to the change area
+2. **Search related docs** — read existing documentation and reference cards related to the change area
 3. **Create a feature branch** and open a PR early (draft is fine)
 4. **Documentation first** — commit doc changes reflecting the desired end state before writing code. This helps the reviewer understand intent and catches design issues early
 5. **Implement** — commit code changes, pushing as you go. The PR gets updated along the way and the user can review and comment at any point
@@ -84,10 +84,7 @@ main ← [card commits] ← [code, close] ← [code, close] ← ... ← [finaliz
 3. A cycle should target a single leaf node (though closing multiple in one cycle is acceptable if the code supports it)
 4. Cycles repeat until the chain is complete
 
-**What is NOT allowed:**
-
-- Introducing a new Mikado card after any code or card-closing commit (new cards require a branch reset — see below)
-- Closing a Mikado card before all cards it depends on have been introduced
+**The one rule:** No Mikado card may be introduced after any code or card-closing commit. New cards require a branch reset (see below).
 
 **The length-zero case:** It is valid for the "planning layer" to have zero commits on the branch — this happens when all Mikado cards were introduced in earlier sessions and are already in main's history. The invariant is satisfied.