rajamesandClaude Opus 5.5
0e2c60dac3
boards/BRINGUP.md R2/R3, FABRIC-3 SXXXIX. The entry stub cleans the cache over the image, builds an identity map (the image's GiB Normal, the rest Device) and enables MMU and caches at EL2 (or EL1); rpi5_mmu.c makes the devicetree's RAM Normal and the framebuffer uncached. Mailbox waits give up after one second; the buffer is cleaned around the exchange; the framebuffer address goes through dma-ranges, not a Pi 4 mask. New rpi5-rehearsal target runs the native image on QEMU virt at EL2. It found three more that would each have stopped the board: the PL011 shift (mine, c9519173; the host test asserted it), the GIC address not carried through /soc's ranges (new fdt_reg_address(), checked against the real Pi 5 DTB), and no timer IRQ at EL2 (HCR_EL2.IMO/FMO/AMO). Rehearsal: POST 1052 passed, same parity hash as UEFI. Standard acceptance on three ISAs: POST 1052, hash 0x82f4ae7cb2e2d424. 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 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.mdis a dated triage snapshot (2026-06-16) and is stale. The authoritative current status lives in.claude/CLAUDE.mdanddocs/fabric/FABRIC-2.md/FABRIC-3.md/FABRIC-3.5.md/FABRIC-3.6.md— not in the status tags inINDEX.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.mdand 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/andlithosananke/ROADMAP.md.
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.