From 116297d7cfbb162bd3db1b9253157a7703cf6090 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 17 Nov 2026 21:52:06 +0000 Subject: [PATCH] docs: record 2026-11-17 -- the regression at 046ce0be, the fault dump, the one heartbeat FABRIC-3 XLVIII.25 covers the day's work: - the regression found at 046ce0be (the fabric step walking every place); - the CI directive and its rulings; - the fault dump, the diagnose stage and the protocol-report fix; - the one adaptive heartbeat; - the protocol on cc09a88b (FAIL: aarch64 stopped in POST); - next, mechanism A. XLVIII.24 is corrected in place: its "no measurable cost" was measured against an already-slow baseline. The Phase 7 plan's Task 3 tick by execution is marked superseded. ENGINE.md section 6 records the tick as settled. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm --- docs/fabric/FABRIC-3.md | 86 +++++++++++++++++++ docs/v4.0.0/ENGINE.md | 1 + ...ngine-step4-phase7-the-loops-and-parity.md | 6 +- 3 files changed, 92 insertions(+), 1 deletion(-) diff --git a/docs/fabric/FABRIC-3.md b/docs/fabric/FABRIC-3.md index c29d0523..a80a3391 100644 --- a/docs/fabric/FABRIC-3.md +++ b/docs/fabric/FABRIC-3.md @@ -6667,5 +6667,91 @@ and memorize frequently so we can pick up where we left off"). - **Seen on amd64:** after POST, `Stadium words: promotions=141`, CONSERVED; POST 539/539; `word_count=377` (the two telling words); `dict_hash` changed once, for the new cell. The boot took 142 s against Phase 1's 153 s: no measurable cost. + **Corrected 2026-11-17:** "no measurable cost" was measured against Phase 1, which was already 1.5 to + 2.4 times slower than f10d2bc8. The regression came in at 046ce0be: every fabric step walked every + place. See 25. - **Next:** Phase 7, the loops on these records (decay, the rolling window, pipelining, inference, L8). + +### 25. The regression found; the fault dump; the one adaptive heartbeat (2026-11-17) + +**The regression.** aarch64 had run out of its 570 s in POST since 37469f6c (990 cases). Captain Bob: +"find out when that happened, and actually start all over no matter how far back you need to go"; "Find +the TCG cost first". +- **Found at 046ce0be**, the mesh boot to spec. The protocol logs give the stage times, for the same + 539-case POST: + + | Arch | f10d2bc8 | 046ce0be | + |---|---|---| + | amd64 | 107 s | 184 s | + | aarch64 | 209 s | 499 s | + | riscv64 | 105 s | 163 s | + + The demo's 87 s boot of 11-06 is a third baseline. +- **Measured** (`logs/20261117-195259/fabric-cost`): about half the boot's time is `v4_fabric_step` + testing every place, nine times a step, when only Hera exists. +- **Not a scheduler.** The rotation is ruled design (ENGINE.md 3d, ruled "A"; MESH.md ruling 7). I had + called it a scheduler, which was wrong. +- **Explained away at the time, never root-caused:** + - Phase 1's "about 90 s before -- the lines now go as messages"; + - Phase 2's comparison with an already-slow Phase 1 (24, corrected); + - Phase 7's "the host slowed". + + The cost method of record (five alternating runs, as for HEAT-OP and A2) was not used after 046ce0be. +- **Write-up:** `docs/v4.0.0/plans/2026-11-17-the-regression-at-046ce0be.md`. **Design:** + `2026-11-17-the-fabric-step-cost.md`. Mechanism A, each pass walking only the places that hold a node, + is ruled and follows the heartbeat. + +**The CI directive** (Captain Bob, the same day): +- POST is as v3's; +- unit tests are the kernel's, with ASan and UBSan; +- three ISAs, one QEMU at a time, in the foreground; +- the EMERGENCY build is a build parameter, and its diagnostic build follows any failure; +- correctness before performance. + +Ruled with it: **every discrepancy is put to him one at a time**, and v3's tests not reproduced as written +is the failure. + +- **The fault dump** (`v4/system/dump.c`; 45b11aec). It prints when a node stops, in every build; a + handled fault keeps its one line. It shows: + - the fault; + - P, A, B; + - both stacks; + - the return stack named by word (the backtrace); + - the running line. +- **`scripts/nightly.sh diagnose`.** After any failed stage it builds the EMERGENCY configuration only, + keeps the artifacts, and is never the result. The protocol and the three workflows run it on failure. + One defect was found and fixed by its own test: it had kept an older build's files when its own build + failed. +- **`protocol-report` fixed** (68fd4854). It had ended silently, writing no PROTOCOL.md, when a boot + stopped before POST's line. + +**The one adaptive heartbeat** (00be5375; plan `2026-11-17-one-adaptive-heartbeat.md`). Captain Bob: +"The adaptive heartbeat is its own thing. It has nothing to do with stadium with any interaction at all. +Not words, not messages, not VMs. It has its own independent RWOT and slope provider. Only one output from +the entire stadium is used as a load measurement for heart rate pacing. ... ONE AS IN THE NUMBER 1 +heartbeat (the adaptive one) runs the entire system." +- **The kernel's heartbeat paces itself** (`heartbeat_pace_from`). Its one input is the Stadium's resident + heat. It keeps its own window and its own slope provider, and Loop #7 sets its own period. +- **Every VM ticks on it, in lockstep.** Each tick is delivered to every node, active or idle. +- **It is held in POST,** so v3's heat cases run as written. +- **The Stadium is charged as before.** +- **What went:** + - the tick by execution (Phase 7 Task 3, "By execution, as v3"); + - the nodes' own Loop #7; + - the timer re-armed from Hera. +- **A first version was withdrawn before commit.** It put the beat on the fabric's steps, Loop #7 on + Hera, and the Stadium charge on the beat. It is kept as superseded in the plan. + +**The protocol on cc09a88b** (`logs/20261117-205521/PROTOCOL.md`): **FAIL**. + +| Stage | Result | +|---|---| +| amd64, riscv64, the stick | POST 990/990, one `dict_hash` (`0x627f392ccbaa96f1`) | +| test-32 | PASS | +| aarch64 | STOPPED at 570 s in POST: the fabric step's cost, unchanged by the heartbeat | + +Pushed at Captain Bob's word (8660ab77). + +**Next:** mechanism A, test first, measured by five alternating runs, then the protocol. + diff --git a/docs/v4.0.0/ENGINE.md b/docs/v4.0.0/ENGINE.md index 6aae5824..cc65ea1c 100644 --- a/docs/v4.0.0/ENGINE.md +++ b/docs/v4.0.0/ENGINE.md @@ -473,5 +473,6 @@ these, a group at a time, with POST after each. | ~~`>R R> R@ I J LEAVE`, which cannot be called~~ Ruled 2026-10-20: they stay in line and are checked when the definition holding them is compiled; every other in-line word is called | Step 3 | | ~~Who decides which node runs next, and when: Hera, by compudynamics; preemptive and cooperative~~ **Settled 2026-11-13 (#189; Captain Bob, "Build it to proper spec"): no one decides -- there is no scheduler (`JUSTIFICATION.md` 4). Every awake node executes an instruction word at each step of the fabric (`v4/include/v4/fabric.h`), and a node with nothing to do waits at a port. The kernel boots the fabric so (`v4/include/v4/mesh.h`).** | Step 7 | | The node's safe moment for message delivery and switching | Step 7 | +| ~~What a node's tick is~~ **Settled 2026-11-17 (Captain Bob: "ONE ADAPTIVE HEARTBEAT. EVERY VM USES THAT ONE CLOCK ... they advance one tick"):** it is the kernel's one adaptive heartbeat. That heartbeat paces itself on the Stadium's resident heat, and every node ticks on it in lockstep at each step of the fabric (`docs/v4.0.0/plans/2026-11-17-one-adaptive-heartbeat.md`) | Step 7 | | `PAD 42 OVER !`, a byte address given to `!` (D-1) | Step 6 | | Which word patrons' accounts the hosted product keeps, having no Stadium | Step 3 | 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 57005d49..a4b56d10 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 @@ -135,6 +135,10 @@ Phase 4). and `:1210`), and its tick is the count of cycles; the timer heartbeat is not the VM's tick. Task 2a had used the kernel's timer: corrected. Each node counts its word calls; every 256th runs its cycle at the call. Test first (`test_mesh_boot.c`, 59 and 67 checks). + **Superseded 2026-11-17** by `2026-11-17-one-adaptive-heartbeat.md` (Captain Bob: "ONE ADAPTIVE + HEARTBEAT. EVERY VM USES THAT ONE CLOCK"). The tick is now the kernel's one heartbeat, and every node + ticks on it in lockstep. The count of word calls, the nodes' Loop #7 and Hera's re-arming of the timer + are removed. The heartbeat is held through POST; FABRIC-3 XLVIII.25. - [x] Background decay (v3's `vm_tick_apply_background_decay`): 64 words a cycle from a cursor down the dictionary, so a word not called cools. The window's adaptive pass (v3's `rolling_window_run_adaptive_pass`): diversity against the last; halve to 256, double to 4096. @@ -145,7 +149,7 @@ Phase 4). trajectories (`make -C v4 inference`). The trajectory from the window's newest words' heat; the window width and slope applied unless it exits early (as v3, the last inferred slope re-applied on a full run even with L6 off). Loop #7: the heartrate 25% slower when stable, 20% faster when - not, within 1/4..4x; Hera's re-arms the kernel's heartbeat. Test first (72 checks; 80 on). + not, within 1/4..4x; Hera's re-arms the kernel's heartbeat (superseded 2026-11-17: Loop #7 is the kernel heartbeat's own, on the Stadium's resident heat). Test first (72 checks; 80 on). amd64 PASS, 163 s. - [x] L8's update (v3's `vm_heartbeat_update_l8` with its table, `ssm_jacquard.c`, `compudynamics.c`): the regime (window entropy >= 0.75, prediction CV >= 0.15, locality >= 1/2, as exact integer