Robert Allan JamesandClaude Sonnet 5
8e2c5dae5f
Not implementation -- documentation-only. M8 is tracked outside Stadium (FABRIC.md §27.5), so this scoping lives in docs/lithosananke/ROADMAP.md rather than as new FABRIC.md 4.3.x items. Read the code before scoping, not assumed: the REPL already works interactively over serial (sk_repl_run(), repl.c) with working backspace/echo, and its on-screen text already renders via the existing VT100 console (vt100_init()/font_8x16.c) independent of both the stroke font and TrueType work -- neither was ever a REPL-strip prerequisite. What's actually missing: sk_readline()'s console_getc() is serial-UART-only, never touches KEY-EVENT (4.3.5f); KEY/?TERMINAL (io_words.c) are dead stubs (KEY calls a getchar() hardcoded to EOF in shim.c, ?TERMINAL always returns false). Resolved design decisions: minimal US-QWERTY scancode->ASCII layout with shift-state tracking (KEY-EVENT carries no modifier state today); merge keyboard into console_getc()'s poll with serial staying a co-equal source, not replaced (the entire acceptance/DoE harness injects over the serial socket -- breaking that breaks make qemu, DOE_INJECT, and every screendump technique used throughout 4.3.x); wire KEY/?TERMINAL to the same merged source for FORTH-79 compliance; CANVAS viewport sizing last, since it's presentation not input plumbing. Extended scancodes, autorepeat-as-character-repeat, arrow-key history explicitly out of scope for the "minimal" bar. FABRIC.md's existing "not yet scoped" notes (4.3.5f's landing-point note, 4.3.7f's closing note) updated to point here rather than duplicating the design content. Co-Authored-By: Claude Sonnet 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.