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

memory: Worldtree U11a — personal flipped to legacy off and verified

Browse Source
This commit is contained in:
vh
2026-09-30 01:21:13 -07:00
parent 9905b76404
commit 060fd92e4e
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistent-memory.md
+3 -3
View File
@@ -1,6 +1,6 @@
# Persistent memory — eshpfi-management
_Last updated: 2026-09-30 ~0120 PT (Worldtree U11a: Prime ruled legacy OFF (not read_only); demo flipped 0115 via the config repo and verified; personal pending its b192 deploy. Prior: Blender extensions, Bonsai spike, phasefinal.com cleanup, U10 backfill.)_
_Last updated: 2026-09-30 ~0122 PT (Worldtree U11a: Prime ruled legacy OFF (not read_only); demo flipped 0115 and personal 0120 via the config repo, both verified. Prior: Blender extensions, Bonsai spike, phasefinal.com cleanup, U10 backfill.)_
> **Always check for `/tmp/infra-ops-handoff.md`** — if it exists and its
> `Written:` stamp is under **8 hours** old, read it (it carries the in-flight
@@ -117,14 +117,14 @@ no longer deployed sidecars here. See Recent decisions.)
_As of 2026-09-30 ~0120 PT._
### Worldtree memory-split: U10 done; U11a legacy OFF live on demo, personal pending (2026-09-30)
### Worldtree memory-split: U10 done; U11a legacy OFF live on demo + personal (2026-09-30)
- U10 legacy backfill DONE: demo 5 filed, personal 797 filed (mimir's 377 `dropped:too_large` are ONE interests record at its ceiling, re-fileable after consolidation; that is the U11 checkpoint's call). Pinned: Prime ruled "leave pinned".
- **U11a: Prime ruled 2026-09-30 0100 (in worldtree-dev's session, thread `01M3RNRC8RE87AJ3M6XBNVHAYP`): legacy plane OFF, not read_only, on demo AND personal, as soon as the b192 image (64f79b38) lands.** The read_only window is skipped. Nothing is deleted; retirement of the old store is the next unit, and worldtree-dev announces it before any data goes. Accepted risk: skaldsong/wizard-v2 on personal, the only Tier-3 client, has unknown record-profile adoption, so its sessions stop being remembered until it adopts the profile. The create log says so per session with a WARNING `will not be remembered until the client adopts the record profile`.
- **Config goes through the config repo, not a hand copy:** `~/development/worldtree-instance-configs` commit 63cf268 adds `memory.writer.enabled: true`, `memory.reader.enabled: true` and `memory.legacy.mode: "off"` to both instances' defaults.yaml. Commit 0a1387e captured the U10 memory_tagger and U9 forget-policy host edits that had never reached the repo. **Both commits are local; pushing them is Prime's call.**
- ⚠ **`off` MUST be quoted.** `core/defaults.py` uses `yaml.safe_load`, which is YAML 1.1: a bare `off` parses as boolean False and the strict `LegacyMode` enum refuses the boot. Verified at 64f79b38 with Worldtree's own `load_cutover_config`. worldtree-dev's recipe had it bare.
- **DEMO flipped at 0115 PT** with `deploy-wt-config deploy demo`. The gauge reads `worldtree_memory_legacy_mode{kind="off"} 1.0`, /health is 200, and the boot log is clean. The staged read_only file is deleted. Rollback: set legacy.mode to `"live"` in the repo and deploy it.
- **PERSONAL pending**: apply when it runs 64f79b38 (staging/v1.0.0b192). ⚠ Personal has **no /metrics**, because the #308 metrics block is demo-only, so the gauge check cannot run there. I asked worldtree-dev to choose between (a) adding the metrics block and (b) a no-metrics proof; default (b) if no answer.
- **PERSONAL flipped at 0120 PT** on 64f79b38a7fb, the same way. ⚠ Personal has **no /metrics**, because the #308 metrics block is demo-only, so the proof was the no-metrics one: an in-container `get_default→load_cutover_config→validate_cutover` gave off/writer/reader True, /health was 200, and the boot log matched the pre-flip one. Whether to add metrics to personal is still worldtree-dev's open call. Both instances are in sync with the repo.
- Watch after each flip: any `legacy executor <kind> invoked with memory.legacy.mode=off; ignored` line goes to worldtree-dev with its stamp.
- **U8 window batches (infra-hermes, Prime's 2340 ruling): likely VOID now that the read_only window is skipped.** The wrapper is NOT built; I asked worldtree-dev whether the plan is dead or has a replacement (e.g. `--legacy-mode off`). If it revives, the harness facts are in thread `01M3RG8RDFSFGDK6BDFTE6ZCJE`, in `persistent-memory.d/2026-09-29-worldtree-u11a-prepped.md`, and as follows. Run it from nh3-dev `~/development/Worldtree`, which is worldtree-dev's tree: NEVER check out or reset it. Each batch takes about 10-15 min, runs under a flock, and must not git-commit; a FAIL goes to worldtree-dev the same day and is never retried.