vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

memory: U11b — writer/reader default to enabled at b193 (no instance action)

Browse Source
This commit is contained in:
vh
2026-10-01 12:35:57 -07:00
parent f37a50c11a
commit 474f78811c
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md
+1
View File
@@ -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.