From 826238e47b4ae1c72cadacd13871fa5dabef9a62 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 13 Nov 2026 21:55:59 +0000 Subject: [PATCH] docs(v4): Phase 7 plan -- Task 2b measured: no cost (#189) Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm --- .../2026-11-13-engine-step4-phase7-the-loops-and-parity.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/v4.0.0/plans/2026-11-13-engine-step4-phase7-the-loops-and-parity.md b/docs/v4.0.0/plans/2026-11-13-engine-step4-phase7-the-loops-and-parity.md index d2560af9..3088a7b8 100644 --- a/docs/v4.0.0/plans/2026-11-13-engine-step4-phase7-the-loops-and-parity.md +++ b/docs/v4.0.0/plans/2026-11-13-engine-step4-phase7-the-loops-and-parity.md @@ -112,6 +112,8 @@ Phase 4). - [x] One departure, ruled by default (Captain Bob did not choose; recorded): v3 promotes a hot word when a lookup finds it in the dictionary; v4's heat is the kernel's, so it is promoted at the call where it is hot. +- [x] Measured: amd64 174 s and 181 s; 2a's own commit booted again just after, 175 s (it was 146 s an + hour before). The host slowed; 2b costs nothing measurable, as the host mesh boot also shows. - **Reported, not changed (v3's own):** with the cache full, v3's promote takes the next slot in turn without looking for the word already there, so a few hot words churn through all 32 slots (`hotwords_cache_promote`, `v3/src/physics_hotwords_cache.c`). v4 does the same. And v3 never calls