rajamesandClaude Opus 5.5
9af442f793
MESH.md step 1, in the engine, which knows nothing of StarForth or of any kernel. - node: V4_PORTS ports (8), a build parameter; "any port" and the port the last such read came from; a read blocks until the neighbour writes, as a write blocks until the neighbour reads; v4_node_born: empty, P at "any port" - exec: a fetch from a port -- @ @b @+ @p, or of an instruction word when P is a port -- waits for a word; a node executes what arrives at a port without advancing P; a blocked node goes on from the slot it stopped at - fabric: the nodes there are and the table of how their ports are wired, both changed while the nodes run; devices on a port; asleep and awake; a step is every unblocked node executing one instruction word, then every write with a reader waiting being handed over - DECOMPOSITION.md section 6: four named ports withdrawn for V4_PORTS numbered ones and wiring as data, as ruled Verified: tests/test_fabric.c, 53 checks at both widths: two nodes exchange words; an empty node is filled through its port by a device, and by another node, and runs what it was sent; a word is passed on by a node in between; a waiting node executes nothing; the wiring is changed while they run; a node is put to sleep, woken and removed while looping; a node is born while others run; the fabric is given more room. make -C v4 test and make -C v4 sanitize pass. The single-node products are unchanged: hosted-check on three ISAs, and clean qemu with STARFORTH_V4=1 on amd64, aarch64 and riscv64 with lines typed at each prompt (logs/20261006-074907, -075150, -075532). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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. Seeformal/CLAUDE.mdfor 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 (Hera/Hermes/Artemis) and the word-level ACL system design.
- 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
- LithosAnanke M7/M7.1 — VM parity validation and init capsule architecture.
See
lithosananke/README.mdandlithosananke/M7.1.md. - Word-level ACL system — Phase 6 complete on
master; Phase 7 (LithosAnanke parity) is the next step. See03-architecture/word-acl/README.md. - Tripod VMs — Hera (governor), Hermes (messenger), Artemis (memory/block
storage). See
03-architecture/tripod/README.mdandbirthing/.
Contributing
- Place new material in
working/first; promote toformal/only when it's ready to be cited (seeformal/CLAUDE.mdfor promotion criteria). - Never touch
patent/,formal/patent/,formal/scraps/legal/, orworking/legal/without Bob's explicit instruction. - Add a
README.mdto any new category-level subdirectory, following the format used throughout this tree: orientation paragraph + bullet list of real files with one-line descriptions.