Files
LithosAnanake/docs
rajamesandClaude Opus 5.5 4da370f492 feat(log): LOG-FLUSH -- a VM's log records reach Artemis's log ring; and the ring keeps its order when it grows
FABRIC-3 SXXXII.4's deferred LOG-FLUSH, built to the 2026-10-14 rulings
(SXXXVIII): everything a VM logs, at or above the log level, goes into its
own buffer; it goes to Artemis on LOG-FLUSH, when full, and at once on an
ERROR, as one kernel-Hermes LOG_BATCH message she writes on her own turn,
the source being the sender the kernel stamped.  Records that cannot go yet
are counted and reported with the next flush.  LOG-SHOW (Hera only) reads
the ring back -- it had no reader.

Found by the first test that filled it: ring growth overwrote the oldest
record and put blank slots inside the live range.  Fixed test first.

Three ISAs: POST 1052 passed; new parity baseline word_count=526
hash=0x82f4ae7cb2e2d424 (deliberate).  CLAUDE.md: Phase 8 PKI closed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 12:10:01 -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.