From f37a50c11a4dd4440f11f3c5ca494cafe0cd44de Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Thu, 1 Oct 2026 11:25:01 -0700 Subject: [PATCH] =?UTF-8?q?memory:=20U11b=20C5=20=E2=80=94=20memory=5Fextr?= =?UTF-8?q?actor=20and=20memory.escalation=20cleared=20to=20retire=20after?= =?UTF-8?q?=20b193?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../2026-09-30-worldtree-u11a-off-u11b-gate.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 2699eae..5926094 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 @@ -34,7 +34,7 @@ **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. +- `model_roles.yaml`: drop `memory_distiller` AND `memory_extractor`. - `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. +- `defaults.yaml`: drop the stale `memory.legacy.mode` comment block, the WHOLE `memory.escalation` block, and any other key b193's boot WARNINGs name as retired (sweep both api logs after the push). +- Why `memory_extractor` can go: `memory.writer.seat` is unset on both (effective `'agent'`, evaluated with `WriterConfig` in both running apis). The other reference, `memory.escalation.model_role`, is inert at b193: `escalation` is in `RETIRED_MEMORY_KEYS`, never parsed, one boot WARNING (worldtree-dev msg 6314). memory_tagger is the only memory role left.