Files
LithosAnanke/docs
Claude 3a70e824a2 feat(v4): Phase 7 Task 2b -- pipelining and the hot-words cache, built, off as v3 (#189)
Rulings, Captain Bob 2026-11-13: "Build a hot-words cache"; then, v3 being found to have both off
(ENABLE_PIPELINING, ENABLE_HOTWORDS_CACHE: n in Kconfig.physics and kernel/Makefile), "Built, off as v3".

- The kernel, at every call (mesh.c): v3's hit check, the transition, the likeliest next word (kept as each
  count rises; v3 scans 1024 a call -- the same word but in a tie v3's Q48.16 rounding makes), speculation
  at v3's thresholds into the node's cache; a word past heat 50 promoted at its call (v3 promotes at a
  lookup; v4's heat is the kernel's). Counters from the owner's heap, given back when a word goes.
- The node (dict.f18): (LOOKUP) tries (HOT)'s xts first, in F18, calling only C@; the kernel keeps it true
  (entries that go, or whose name is defined again, taken out). Empty unless the build has the cache.
- Tests: test_mesh_boot.c as built (57 checks) and with both on (mesh-boot-on, 65). v4 test: all pass.
- Reported, v3's own: when full, its promote takes the next slot without looking for the word there (a few
  hot words churn all 32 slots); its prefetch misses are never counted. Both reproduced.
- amd64 boots, RESULT: PASS, but 174 s and 181 s against 2a's 146 s, while on the host the mesh boot is no
  slower: being measured. Not pushed (held to the Phase 7 boundary).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-13 21:52:01 +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.