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
StarForth / LithosAnanke documentation — the map
Start here. This page says where each kind of document lives and which one to believe. Reorganised 2026-10-14 (the docs triage): one place for current reference, one archive for everything kept as record, and every superseded or abandoned document labelled as such in its own header.
- INDEX.md — every document in the repository, with its status.
- DEAD-AND-REVISED.md — the ideas that were abandoned, and the claims that were revised, each with the date and where the decision is recorded.
- DELETE-CANDIDATES.md — what was deleted as duplicate, and why (2026-10-14).
What to believe
| For | Authoritative | Where |
|---|---|---|
| How to work in this repo, and current status | .claude/CLAUDE.md |
repo root |
| What was decided, and why; work as it happened | the FABRIC record | fabric/ — FABRIC-3.md is the living one |
| StarForth v4 (the F18-derived engine) | the v4 design | v4.0.0/ and ../v4/README.md |
| Roadmap and release-versioning policy | ROADMAP.md |
reference/ |
| Getting onto the boards | the bring-up checklist | ../boards/BRINGUP.md |
| A word, a primitive, a term | the dictionaries and the ontology | reference/ |
| What the code does | the code, and its folder's README.md |
../kernel/, ../v3/, ../v4/ |
Where two documents disagree, the one higher in this table wins, and code wins over all.
Layout
- fabric/ — the design and work record, numbered in order.
FABRIC-3.md(bare-metal boot and everything since) is open; the others are closed:- FABRIC-0, -1 and -2 are history;
- FABRIC-3.5 and -3.6 are the Tripod/kernel reshuffle, still authoritative for what they ruled;
- FABRIC-3.7 (elevation) is closed as not needed;
- FABRIC-4 holds ideas caught early, not yet scoped.
- v4.0.0/ — StarForth v4: justification, engine, decomposition, nucleus, mesh,
parity with v3.
plans/holds the step plans, all executed. - reference/ — current reference material:
ROADMAP.md(roadmap and the ratified versioning policy);M7.1.md(init capsules and birth);word-acl/(the word-level ACL design);kernel-args/(the boot command line);hosted-acceptance-test/;DICTIONARY.mdandSTARFORTH_PRIMITIVES.md(the words);ONTOLOGY.md(the lexicon);L8_ADAPTIVE_CONFIG_TABLE.md.
- working/ — living material and the source for
formal/:architecture/(design notes and HOWTOs);experiments/(DoE designs and campaign data);papers/(academic sources, the system narrative, proposals);hardware/,specifications/andscratch/;archive/, which has four parts:historical/: finished work, kept as record;superseded/: replaced, and each file's header names what replaced it;dead/: abandoned or never adopted;- the older
legacy/,quality/,operations/,research/andsession-logs/.
- formal/ — the press-ready LaTeX tier (three volumes, books, standalone
reports). Governed by
formal/CLAUDE.md. - book/ — the LithosAnanke and StarForth book build.
- pptx/ — slide decks for different audiences.
- patent/ — provisional patent material. Legal hold: ask Captain Bob before
touching anything here (also
formal/patent/,formal/scraps/legal/,working/legal/).
Adding a document
- Draft in
working/; promote toformal/when it is ready to be cited (formal/CLAUDE.md). Reference material that describes the system as it is goes inreference/. - When a document is overtaken, do not delete it:
git mvit intoworking/archive/superseded/ordead/with a header saying why and what replaces it, and add a line toDEAD-AND-REVISED.md. - Rules for documentation work: CLAUDE.md.