From 9905b764043e3af8a87db8825b0c12b6bbbbc584 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Wed, 30 Sep 2026 01:17:23 -0700 Subject: [PATCH] =?UTF-8?q?memory:=20Worldtree=20U11a=20=E2=80=94=20Prime?= =?UTF-8?q?=20ruled=20legacy=20off;=20demo=20flipped=20via=20config=20repo?= =?UTF-8?q?=20and=20verified;=20personal=20pending?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- persistent-memory.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/persistent-memory.md b/persistent-memory.md index e23764c..e3d0e23 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -1,6 +1,6 @@ # Persistent memory — eshpfi-management -_Last updated: 2026-09-29 ~2345 PT (Blender extensions live on both paths + blender-run --cpu; Bonsai spike + MMVQ follow-up + weights acquired; phasefinal.com cleanup live; Worldtree U10 backfill done on demo+personal, U11a prepped (staged, not flipped); NEXT: build the U8 gate-batch wrapper for infra-hermes, Prime ruled 2340.)_ +_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.)_ > **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 @@ -115,18 +115,18 @@ no longer deployed sidecars here. See Recent decisions.) ## Current state / in-flight -_As of 2026-09-29 ~2345 PT._ +_As of 2026-09-30 ~0120 PT._ -### Worldtree memory-split: U10 done, U11a prepped, U8 window wrapper IN PROGRESS (2026-09-29) +### Worldtree memory-split: U10 done; U11a legacy OFF live on demo, personal pending (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 (`memory.legacy.mode` read_only): demo runs 78a509b90267 (U11a code) and boots `live`, proven by the gauge `worldtree_memory_legacy_mode{kind="live"} 1.0` on `127.0.0.1:8080/metrics`. The INFO boot line is not emitted in this deployment's logs. The flip config is STAGED and inert at `/opt/worldtree/config/defaults.yaml.staged-u11a-read_only` on corviduo-dev. **The flip waits on Prime's go**, relayed by worldtree-dev (thread `01M3RGGYR5EHKZVGM7ABM5RMTF`). Apply = back up, copy over `defaults.yaml`, `docker restart worldtree-worldtree-api-1`, then check that the gauge reads read_only=1. Open Prime ruling: skaldsong/wizard-v2, personal's only Tier-3 client, has unknown record-profile adoption. -- **IN PROGRESS, Prime's ruling of 2026-09-29 ~2340: "infra-hermes runs the batches, go ahead".** Pending: build a wrapper (e.g. `scripts/wt-memory-gate-batch`) around worldtree-dev's U8 harness, then brief infra-hermes to run one batch per day through the read_only window, with infra-ops on escalation. Harness facts (worldtree-dev thread `01M3RG8RDFSFGDK6BDFTE6ZCJE`): - - nh3-dev `~/development/Worldtree`, pinned to demo's deployed SHA. The main checkout was at 78a509b9, the same as demo, at 2340. It is worldtree-dev's working tree: NEVER checkout or reset it; use a separate `git worktree` if the SHAs diverge. - - Command: `source .venv/bin/activate && source env.sh && python -m core.memory_acceptance.live --runs 3 --gate --legacy-mode read_only --label window`. - - Output lands in `docs/eval/memory_acceptance_runs/Z/`. The verdict is in `trace1.md`: `Aggregate label: **gate**, verdict: **PASS|FAIL**`. Report the Semantic axis section when the judge was not controlled, but do not fail on it. - - About 10-15 min per batch; needs the LiteLLM gateway; never two at once (flock); FAIL goes to worldtree-dev the same day with the run stamp, never a retry; the wrapper must NOT git-commit (worldtree-dev commits the run dirs). - - Ask worldtree-dev whether daily batches start now or at the flip. +- **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. + - Watch after each flip: any `legacy executor 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. ### nh3-pve + nh3-ml1: post-visit, all live (2026-09-25/26)