diff --git a/claude/memory/MEMORY.md b/claude/memory/MEMORY.md
index 8822f20..5e01f81 100644
--- a/claude/memory/MEMORY.md
+++ b/claude/memory/MEMORY.md
@@ -18,6 +18,7 @@ permalink: claude-memory/memory
 **Rules that fire silently — keep these in front of me**
 - [Fowler's rules for quotation](feedback_fowlers_rules_quotation.md) — single quotes primary, double for nested, logical British punctuation order. All writing.
 - [Canadian spelling in ARC prose](feedback-canadian-spelling-arc-prose.md) — centre/colour ("almost EU"). Draft all steward-voiced prose this way; corpus "center" = autocorrect drift (cleanup open).
+- [Governance is the toll, not the road](feedback-governance-is-the-toll-not-the-road.md) — steward 2026-09-20: **out of purely governance work, back to project progress.** ⚠ **"Order by urgency" KEEPS him there** — every urgent item is governance. **Split the backlog into RULINGS (a morning) vs WORK (a week) before planning**; rank a ruling by what it RELEASES. 11 of last 12 sessions governance-dominant.
 - [Close thoroughly — no frequent deferrals](feedback-close-thoroughly-no-frequent-deferrals.md) — **frequent deferrals ARE how the cloud accumulated.** Close ALL of a block that's closable-now; for the rest, **name the specific dependency**.
 - [Shorter, concentrated sessions](feedback-shorter-concentrated-sessions.md) — ONE tightly-scoped high-leverage bite taken all the way, then wrap; hold the rest as ranked horizons.
 - [Constitution-as-block, then pull-based corpus](feedback-constitution-as-block-then-pull-based-corpus.md) — finish the **constitution as one block FIRST**, then corpus-into-spec **pulled by what each engine phase needs**. **Bounded question → bounded answer**; keep open-thread count LOW.
diff --git a/claude/memory/feedback-governance-is-the-toll-not-the-road.md b/claude/memory/feedback-governance-is-the-toll-not-the-road.md
new file mode 100644
index 0000000..3d81ab0
--- /dev/null
+++ b/claude/memory/feedback-governance-is-the-toll-not-the-road.md
@@ -0,0 +1,45 @@
+---
+name: feedback-governance-is-the-toll-not-the-road
+description: "The steward wants out of purely governance work and back to progress across the projects. Measured 2026-09-20: eleven of the last twelve sessions were governance-dominant, nine with no project signal at all. ⚠ Ordering by urgency KEEPS him there, because every urgent item is governance — but the urgent tier is RULINGS (a morning) not WORK (a week). Separate the two before planning."
+metadata:
+  node_type: memory
+  type: feedback
+  modified: 2026-09-20
+---
+
+# Governance is the toll, not the road
+
+**Steward, 2026-09-20, at the wrap:** *"I would like, if possible, to come out of purely governance
+work and get back to making progress across our various projects."*
+
+**Why:** The governance apparatus exists to make the project work trustworthy. It is not itself the
+work. When the register becomes the thing being tended, the apparatus has inverted its purpose —
+and nothing in the register's own machinery can notice that, because every instrument in it measures
+the register. **Measured 2026-09-20** over the last twelve session memories: **eleven
+governance-dominant, nine with zero project signal**, the last clearly project-led session being
+**2026-09-03**. ⚠ *Crude instrument — a keyword ratio over each file's opening; the direction is
+unambiguous, the magnitude is not.* Roughly three weeks.
+
+**How to apply:**
+
+- ⚠ **"Proceed in order of urgency" will keep him in governance**, because every urgent item is a
+  governance item. Do not resolve this by quietly re-ranking — **say it**, then separate the two
+  kinds of item, which is what actually dissolves the conflict.
+- **Split the governance backlog into RULINGS and WORK before planning anything.** A ruling is a
+  decision the steward makes in a sitting from a stated option set; work is a census, a build, a
+  measurement, or a repair that has to be scheduled. **The urgent tier of 2026-09-20 was four
+  rulings and one small mechanism — a morning, not a week.** Rulings are cheap in wall-clock time
+  and they *unblock* project work; treating them as "more governance" is the error.
+- **A ruling that unblocks many items outranks an item that is merely older.** PENDING-146 gates
+  about fourteen; the joint PENDING-178/-179 ruling discharges three obligations at once. Rank by
+  what a decision *releases*, not by age or by tag.
+- **Name the project work that is already unblocked and say so out loud** — it is invisible under a
+  register that lists only what is open. On 2026-09-20 that was PENDING-187 (authorized, ready at
+  slice 1) and one unread file from Seb that would either unblock five L1 items or confirm the block.
+- **Governance findings will keep arriving mid-project — that is fine and expected.** File them and
+  keep going. What the steward is asking to end is the *session whose whole content is the register*,
+  not the discipline of recording what surfaces.
+- 🎻 **He is a working musician.** Deadlines like D821 (2026-10-01) are not a distraction from the
+  work; they are the life the work is meant to serve. Weight them in any weekly plan.
+
+Related: [[feedback-shorter-concentrated-sessions]] · [[feedback-close-thoroughly-no-frequent-deferrals]] · [[feedback-constitution-as-block-then-pull-based-corpus]]