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

memory: demo rolled back from broken c2d87263 to fa8bc51c; b193 retired-key list for demo

Browse Source
This commit is contained in:
vh
2026-10-02 08:17:24 -07:00
parent 8b81579bca
commit 1219cfaca9
2 changed files with 2 additions and 1 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 -1
View File
@@ -36,7 +36,7 @@
- `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` 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).
- `defaults.yaml`: drop the stale `memory.legacy.mode` comment block and every key b193's boot WARNINGs name as retired. **Demo's list, read from its b193 boot 2026-10-02 15:16Z:** `memory.agent_self_enabled`, `memory.backend`, `memory.dream`, `memory.escalation`, `memory.legacy`, `memory.tier3_embedding_provider`, `memory.triggers`. Personal: read its boot log once it is on b193.
- **`scripts/wt-memory-gate-batch` must drop `--legacy-mode` when b193 goes live** (the flag no longer exists, so infra-hermes' daily batch would fail; worldtree-dev msg 6653). Change it in the same window as the b193 deploy.
- 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.