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

memory: U11b step 5 done — live legacy memory deleted on demo and personal (H2 0), stamp sent

Browse Source
This commit is contained in:
vh
2026-10-02 07:54:50 -07:00
parent b0789f4b29
commit 1cc8ad3292
2 changed files with 3 additions and 7 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
@@ -14,7 +14,7 @@
**The U11b gate (Prime 0320 via worldtree-dev, thread `01M3SGEQDRQD7DWBVT4K73FAHP`):** **The U11b gate (Prime 0320 via worldtree-dev, thread `01M3SGEQDRQD7DWBVT4K73FAHP`):**
- DELETE the live legacy data on both instances after **3 consecutive PASS batches at off**. A FAIL restarts the count. - DELETE the live legacy data on both instances after **3 consecutive PASS batches at off**. A FAIL restarts the count.
- infra-hermes runs the daily batch, `scripts/wt-memory-gate-batch`, in a detached worktree at demo's deployed sha. Its exit codes are 0 PASS / 1 FAIL / 2 error / 3 refused / 4 busy. - infra-hermes runs the daily batch, `scripts/wt-memory-gate-batch`, in a detached worktree at demo's deployed sha. Its exit codes are 0 PASS / 1 FAIL / 2 error / 3 refused / 4 busy.
- Count: **3 of 3, complete** — 20260930T090608Z PASS (user median 0.83); 20261001T143101Z PASS (first daily batch, infra-hermes, cc msg 6179); 20261002T143101Z PASS (user median 0.83 over runs [0.92, 0.83, 0.83], msg 6649). Step 5 held 2026-10-02 0750 for Prime's direct go (the ruling was relayed). The 0930 run started by accident from a test meant to be `--dry-run`. worldtree-dev's controls 080927Z and 082829Z each FAILed by one flip and were the instrument check, not the streak. - Count: **3 of 3, complete** — 20260930T090608Z PASS (user median 0.83); 20261001T143101Z PASS (first daily batch, infra-hermes, cc msg 6179); 20261002T143101Z PASS (user median 0.83 over runs [0.92, 0.83, 0.83], msg 6649). Step 5 held 2026-10-02 0750 for Prime's direct go (the ruling was relayed); he gave it in infra-ops' channel and it was DONE at 14:54:03Z (H2 0/0 before and after, both apis healthy, stamp sent). The 0930 run started by accident from a test meant to be `--dry-run`. worldtree-dev's controls 080927Z and 082829Z each FAILed by one flip and were the instrument check, not the streak.
- Step 5 is mine: - Step 5 is mine:
1. Run `scripts/wt-h2-count.py` VERBATIM inside each api container. The rehearsal on copies read 0 on both instances. 1. Run `scripts/wt-h2-count.py` VERBATIM inside each api container. The rehearsal on copies read 0 on both instances.
2. Delete LIVE, with the api running, using literal paths. 2. Delete LIVE, with the api running, using literal paths.
persistent-memory.md
+2 -6
View File
@@ -137,12 +137,8 @@ _As of 2026-10-01 ~0446 PT._
### Worldtree U11 memory cutover (demo + personal) ### Worldtree U11 memory cutover (demo + personal)
- **Legacy plane OFF since 0115/0120 PT 2026-09-30** (config repo 63cf268; personal /metrics b6fdd81; the repo is pushed). → `persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md` - **Legacy plane OFF since 0115/0120 PT 2026-09-30** (config repo 63cf268; personal /metrics b6fdd81; the repo is pushed). → `persistent-memory.d/2026-09-30-worldtree-u11a-off-u11b-gate.md`
- **Daily gate batches:** infra-hermes runs `scripts/wt-memory-gate-batch` from 2026-10-01 and copies me on every verdict. The count is **3 of 3 — STREAK COMPLETE** (20260930T090608Z, 20261001T143101Z, 20261002T143101Z, msg 6649). **STEP 5 is armed but HELD for Prime's direct go in infra-ops' own channel** (the ruling reached me only via worldtree-dev; no relayed authorization for a deletion, even with the archive as a restore path). Verdict ccs arrive FROM `hermes-gateway`, which is pull-only and never read, so send replies to `infra-hermes`. - **U11b STEP 5 DONE 2026-10-02 14:54:03Z on Prime's direct go** (in this channel, ~0750 PT). H2 re-check exit 0 on both (demo rows 4/12/5, personal 0/6/2200, agent_self 0); deleted `agents/{forseti,lofn,mimir}/memory/<agent>.chroma` + `memory/context_promotion` on demo and personal with literal paths; apis healthy, no restart; stamp sent to worldtree-dev (b193 is theirs to cut). Demo had already lost 22 context_promotion JSONL (2026-07-03) to ledger.py's 90-day `JSONL_RETENTION_DAYS` sweep on 10-01 07:10:30 — TTL, not an erasure; flagged to worldtree-dev as retirement owner.
- **⚠ U11b STEP 5 IS MINE, triggered by the 3rd consecutive PASS:** - **On b193 day (mine):** drop `--legacy-mode` from `scripts/wt-memory-gate-batch` (infra-hermes' daily batch fails otherwise); remove the residue `memory/context_promotion/ledger.db` a b192 restart may have re-created; then the parity config retirements (detail file). Verdict ccs come FROM `hermes-gateway` (never read); reply to `infra-hermes`.
1. Run `docker exec -i <api> python - < scripts/wt-h2-count.py` VERBATIM, right before each instance's deletion. Exit 2 means STOP and send worldtree-dev the output.
2. Delete LIVE, with the api running, using literal paths only: `agents/{forseti,lofn,mimir}/memory/<agent>.chroma` and `memory/context_promotion`, on BOTH instances.
3. Send worldtree-dev the stamp; b193 ships after it.
- A b192 restart re-creates an empty schema-only `ledger.db`. That is residue: say so in the stamp and remove it after b193.
- **Legacy archive:** DESTROY it whole by **2026-10-30**, or at retirement-done, or on a subject-erasure request, whichever comes first. The runbook is in the detail file. - **Legacy archive:** DESTROY it whole by **2026-10-30**, or at retirement-done, or on a subject-erasure request, whichever comes first. The runbook is in the detail file.
- **TODO:** re-sweep both api logs after real traffic. After the b193 push, remove the retired config keys (list: detail file, "Post-b193 config retirements"). - **TODO:** re-sweep both api logs after real traffic. After the b193 push, remove the retired config keys (list: detail file, "Post-b193 config retirements").