Captain Bob, 2026-11-17: "The adaptive heartbeat is its own thing ... 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." Ruled one at a time: the kernel's heartbeat; resident heat its one input; held in POST; the Stadium charged as before today (docs/v4.0.0/plans/2026-11-17-one-adaptive-heartbeat.md, its first version kept as superseded). - kernel/src/heartbeat.c, timer.h: heartbeat_pace_from(load) -- its own window of samples, its own slope provider (v4's inference arithmetic) every HEARTBEAT_PACE_EVERY samples, Loop #7 setting its own period (not stable 20% faster, stable 25% slower, 1/4..4x the 10 ms base). No source (v3's path): nothing runs. - kernel/src/vm/stadium.c: stadium_resident_heat_total(), read only -- the one output it paces by. - v4/system/mesh.c, mesh.h: the owner's clock read at every fabric step; each tick delivered, one by one, to every node present -- its heartbeat cycle run, active, idle or blocked alike. The tick by execution, the nodes' own Loop #7 and the heartrate callback are gone. - kernel/src/v4/sk_v4.c: the clock gives the heartbeat's bottom half its turn; 0 until POST has ended. - Tests first, each seen to fail (does not build): kernel/tests/test_heartbeat.c (11 checks), test_stadium_node.c (16), test_mesh_boot.c's lockstep checks. Seven Phase 7 checks that assumed the tick by execution now drive the test's heartbeat (ruled). POST 990/990 with v3's heat cases as written; mesh-boot 103, -on 112, -noop 100, san-mesh-boot 103, every v4 program at both widths, every kernel host test: 0 failures. The full `sanitize` target not run (it outlasts the foreground limit). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
include/starkernel/vm/
Headers for the kernel-side VM subsystem (src/starkernel/vm/).
arena.h— the capsule arena allocator: fixed-region allocation for capsule payload data, separate fromkmalloc's general kernel heap.parity.h— the birth/execution parity-record logger: declares the logging interface used to record VM ID, capsule content hash, and dictionary hash on every capsule birth, enabling offline determinism verification across independent kernel runs.
See include/starkernel/vm/bootstrap/README.md for the VM bootstrap
subsystem.