Files
LithosAnanke/docs
Claude 046ce0be65 feat(v4): the mesh boot to spec -- Hera born empty in the kernel's fabric; births, kills, every node stepping together (#189)
ENGINE step 4 Phase 1, Tasks 5b-5d, and the edge cases (Captain Bob, 2026-11-13: "Build it to proper
spec"; "Check for the edge cases"; "Yes, add it to v4-checks").

- v4/system/mesh.c, v4/include/v4/mesh.h: the nucleus assembled by the ROM and given to Hera as F18
  cells; Hera born empty at place 0, the kernel on port 0, the console on port 1; told she is 10, in the
  registry, the kernel's words, FORTH-79, sealed, POST, the kernel's capsules. NODE-BORN / NODE-KILL in
  the owner's room.
- No scheduler: v4_mesh_tell returns once the node told says how its text ended, and
  v4_mesh_step / v4_mesh_busy let the host step the fabric while it waits, so nodes run between
  lines as during them. A text left "waiting" is owed its end: the next line ends it "Interrupted"
  and is then run (MESH.md 7b.6).
- kernel: sk_v4.c boots through the mesh; its idle steps the fabric while a node can run, and halts
  only when none can (#151 kept). stadium_return_quota and stadium_ops_forget on a kill.
- Tests: v4/tests/test_mesh_boot.c (32 checks: the boot, births, kills, rebirth, a live number, a
  fault, no such node, Hera not killing herself, no room, a line too long, a node running for ever,
  a wait broken by the next line), run by `make -C v4 test` and under ASan+UBSan by `sanitize`
  (v4-checks); kernel/tests quota return; scripts/qemu_session.py births() and the edges on bare
  metal.
- Docs: ENGINE.md 6 "who runs next" struck (settled: no scheduler); the Phase 1 plan; FABRIC-3
  XLVIII.23; .claude/memory/rules.md: alpha.5 closed to new work.
- Evidence: v4-checks 80 programs under the sanitizers, 0 failures; the hosted builds alike; two
  stopped v4-checks runs labelled STOPPED; three development amd64 boots labelled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-13 17:00:08 +00:00
..
…
…
…
…

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.md and STARFORTH_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/ and scratch/;
    • 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/ and session-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 to formal/ when it is ready to be cited (formal/CLAUDE.md). Reference material that describes the system as it is goes in reference/.
  • When a document is overtaken, do not delete it: git mv it into working/archive/superseded/ or dead/ with a header saying why and what replaces it, and add a line to DEAD-AND-REVISED.md.
  • Rules for documentation work: CLAUDE.md.