rajamesandClaude Opus 5.5
6a019b8968
DECOMPOSITION.md 5.8 only named these as "standard pictured-output definitions over UM/MOD and a hold buffer". They are now written out (5.8) and run on the golden model. D-13 (ruled 2026-10-03): the hold buffer takes 63 characters, as v3's; HOLD of a value outside 0-255, or into a full buffer, stores nothing and sets NODE-ERROR, which is what v3 did with its error flag. Behaviour follows v3 otherwise: digits 0-9 then A-Z, BASE outside 2..36 reads as 10, SIGN ( n -- ). Stack effects are the standard ones, as 5.8 already ruled (v3 took its double low cell on top). The buffer is 64 bytes, filled backwards from its end through HLD; `#` divides by the base in two UM/MOD steps. HOLD, SIGN and # end in a jump to the next word instead of a call, which saves two return-stack entries: with calls, the signed picture `.` needs overflowed the 9-deep return stack. New test file v4/tests/test_pictured.c, on a node of its own: test_foundation.c's hand-assembled words already fill 901 of a node's 1024 words. It re-assembles SWAP, OR, UM/MOD, LSHIFT, RSHIFT and C! as they are in test_foundation.c. Checked against a C reference (short division on 16-bit limbs) at 32- and 64-bit cells, optimised and ASan+UBSan (`make test`, `make sanitize`), 4716 checks per width: <# #S #>, <# # # 46 HOLD #S #> and the signed picture, in bases 10, 16, 2, 8, 36, 3 and the invalid 0, 1, 37, -5, on every pair of 15 edge cells; HOLD of 12 values; and a base-2 number that overflows the buffer (63 characters kept, NODE-ERROR set, nothing outside the buffer written). Six mutations all fail. Headroom: <# #S #> leaves 3 data cells and 2 return entries; the signed picture leaves 1 return entry. The depth is C!'s as written (C! -> LSHIFT -> SWAP), which is unchanged. Test results on the amd64 host only. This is a development check, not acceptance (JUSTIFICATION.md section 16). 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.