diff --git a/persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md b/persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md
index 8b92768..2699eae 100644
--- a/persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md
+++ b/persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md
@@ -31,3 +31,10 @@
   2. `rm /volume1/Backup/restic/nh3-dev/wt-legacy-archive` on nh3-nas.
   3. The ana-nas mirror's `--delete` follows; verify it.
   4. `secret rm` the password AND purge Vaultwarden's trash (crypto-shred), and check for NAS share snapshots.
+
+**Post-b193 config retirements (U11b C5, worldtree-dev msg 6312, 2026-10-01).** Parity-only, no boot effect; apply via `deploy-wt-config` at my pace AFTER b193 is live, both instances:
+- `policies.yaml`: drop the memory-dream-allow rule and admin-everything's `exclude_actions: [memory.dream]` (the action is gone; a policy naming it is inert).
+- `model_roles.yaml`: drop `memory_distiller`. `memory_extractor`: OPEN, see below.
+- `providers.yaml`: KEEP the `summarizer` catalog entry (the deprecated granite-4.1-8b preset still binds `catalog_id: summarizer`; dangling = boot error); only its description changes.
+- `defaults.yaml`: drop the stale `memory.legacy.mode` comment block (the key already warns as retired since C2).
+- **`memory_extractor` is NOT clear to drop.** `memory.writer.seat` is unset on both (effective `'agent'`, evaluated with `WriterConfig` in both running apis), BUT `memory.escalation.model_role: memory_extractor` sits on both (escalation disabled). Reported to worldtree-dev; whether b193 resolves it while disabled decides it.
diff --git a/persistent-memory.md b/persistent-memory.md
index dd5e13b..7c52f44 100644
--- a/persistent-memory.md
+++ b/persistent-memory.md
@@ -144,7 +144,7 @@ _As of 2026-10-01 ~0446 PT._
   3. Send worldtree-dev the stamp; b193 ships after it.
   - A b192 restart re-creates an empty schema-only `ledger.db`. That is residue: say so in the stamp and remove it after b193.
 - **Legacy archive:** DESTROY it whole by **2026-10-30**, or at retirement-done, or on a subject-erasure request, whichever comes first. The runbook is in the detail file.
-- **TODO:** re-sweep both api logs after real traffic. After the b193 push, remove the retired config keys.
+- **TODO:** re-sweep both api logs after real traffic. After the b193 push, remove the retired config keys (list: detail file, "Post-b193 config retirements").
 
 ### fv-ml1 GPU layout (as of 2026-10-01)