Files
LithosAnanake/docs
rajamesandClaude Opus 5.5 c15589b39e fix(vm): a text run from inside a line no longer takes the line's place -- LOAD and THRU go on with the rest of it
FABRIC-3.md XXXIV.1, traced and fixed.  vm_interpret() copied each text
into the VM's one input buffer and reset the position.  LOAD runs its
block by calling it, so the block replaced the line LOAD was on and
nothing after LOAD or THRU on that line was ever interpreted; the same
for -->, a capsule's EXEC and a message kernel-Hermes delivers.
vm_interpret() now keeps what the outer text had not yet read when it is
called from inside another, and puts it back after, as FORTH-79's LOAD
keeps the input stream it interrupts.  In the kernel's VM and the hosted
one alike.

POST: LOAD.rest_of_line (1 LOAD 0 0 /) and THRU.rest_of_line
(1 2 THRU 0 0 /) failed without the fix (logs/20261014-061222) and pass
with it.  Three-ISA acceptance: logs/20261014-061508 (amd64), -061624
(aarch64), -061837 (riscv64), 1052 tests, none failed, zuse prompt,
hash 0x08873e0f44b7cb2a unchanged.  The hosted binary: 100 LOAD 1 + .
gives 8.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 06:19:54 -04:00
..

StarForth / LithosAnanke Documentation

This is the lithosananke branch: the bare-metal StarKernel side of the project (contrast master, which is the hosted-VM-only side). Documentation follows the two-tier model described in docs/CLAUDE.md: formal/ is the polished, citable LaTeX tier; working/ is living design notes and drafts that feed it. Everything else in this directory is branch- or subsystem-specific material that doesn't fit either tier.

Layout

  • formal/ — Three-volume LaTeX documentation set (research volumes, practitioner books, standalone reports) plus the scraps/ fragment library it's assembled from. Audience: patent counsel, SSRN reviewers, licensees, hobbyists with hardware in hand. See formal/CLAUDE.md for authoring conventions.
  • working/ — Living documents: architecture design notes, DoE experiment logs, hardware/platform notes, draft specs, academic-paper source material, and an archive of superseded docs. Source material for formal/.
  • 03-architecture/ — Tripod VM architecture constraints and the word-level ACL system design. (Note: the fleet is now Hera/Artemis/Hestia post- reshuffle; the old Hera/Hermes/Artemis framing in older docs is historical. The older, triaged copy of this tree is working/architecture/03-architecture/.)
  • lithosananke/ — LithosAnanke kernel branch documentation: milestone roadmap, system architecture, HAL reference, kernel command-line argument design, and the amd64 APIC-timer ISR postmortem.
  • birthing/ — VM birthing plan and status for the Hera-spawns- Hermes/Artemis constellation, plus three-architecture QEMU acceptance logs.
  • patent/ — Provisional patent application source. Legal hold — ask Bob before touching anything in this directory.
  • api/ — Generated Doxygen tag file and warnings log (gitignored; not part of the tracked doc tree).
  • pptx/ — Elevator-pitch and deep-dive slide decks for different audiences (technical, non-technical, academic, PhD-level).

Current Active Work

⚠ INDEX.md is a dated triage snapshot (2026-06-16) and is stale. The authoritative current status lives in .claude/CLAUDE.md and docs/fabric/FABRIC-2.md / FABRIC-3.md / FABRIC-3.5.md / FABRIC-3.6.md — not in the status tags in INDEX.md.

  • LithosAnanke M7.1 — live — init capsules, the Tripod fleet, Stadium physics-economy, and word-level ACL (Phases 1–7 complete; Phase 8 Ed25519 PKI pending). See lithosananke/ROADMAP.md and the FABRIC documents above.
  • Tripod VMs (post-reshuffle) — Hera (governor), Artemis (memory/block storage), Hestia; the Hermes VM was removed and messaging moved into the kernel as kernel-Hermes. See .claude/CLAUDE.md.
  • StarForth v4 — the F18-derived 32-opcode engine with the node/mesh design. See v4.0.0/ and ../v4/README.md.
  • Word-level ACL system — see 03-architecture/word-acl/ and lithosananke/ROADMAP.md.

Contributing

  • Place new material in working/ first; promote to formal/ only when it's ready to be cited (see formal/CLAUDE.md for promotion criteria).
  • Never touch patent/, formal/patent/, formal/scraps/legal/, or working/legal/ without Bob's explicit instruction.
  • Add a README.md to any new category-level subdirectory, following the format used throughout this tree: orientation paragraph + bullet list of real files with one-line descriptions.