From 474f78811c4a596ae10af49065366c1e91f45971 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Thu, 1 Oct 2026 12:35:57 -0700 Subject: [PATCH] =?UTF-8?q?memory:=20U11b=20=E2=80=94=20writer/reader=20de?= =?UTF-8?q?fault=20to=20enabled=20at=20b193=20(no=20instance=20action)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md | 1 + 1 file changed, 1 insertion(+) 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 5926094..197a82d 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 @@ -37,4 +37,5 @@ - `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 WHOLE `memory.escalation` block, and any other key b193's boot WARNINGs name as retired (sweep both api logs after the push). +- No action, for the record (msg 6380): at b193 `memory.writer.enabled` / `memory.reader.enabled` default to TRUE. Both instances set them `true` explicitly; KEEP those lines (explicit over implicit). A `false` would now boot with one WARNING. - 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.