Captain Bob, 2026-10-14: "v4 is the default build", "no, qemu to v4 too ... we are effectively trying to retire v3", "the 32 bit build needs to go into the acceptance test too", "i don't care about v3". - STARFORTH_V4 defaults on (Kconfig default y) and V4_DEFAULT=1 everywhere: every kernel carries v4 and v3 and boots v4; system=v3 boots v3; STARFORTH_V4=0 builds v3 alone. Board images write system=v4. - Acceptance (CLAUDE.md): the three ISAs as built (v4, POST passed, V4_SYSTEM dict_hash equal) and make -C v4 test-32. v3 is not part of it. Acceptance run: amd64, aarch64, riscv64 -- PARITY:V4_POST 538/538, dict_hash=0xe5a57f3eb72ff94a on all three, no unknown word; test-32: 30 suites, 0 failures. The SER5 image under OVMF boots v4 as built, v3 after the one-word edit. README, BRINGUP, FABRIC-3 XLIII, the register updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.