rajamesandClaude Opus 5.5
7aed588f78
docs/CLAUDE.md Phase 2, 2026-10-14. All moves by git mv; every archived file carries a header saying what it is, why, and where to look instead. - docs/reference/ (new): roadmap and versioning policy, M7.1, word-ACL design, kernel args, hosted acceptance test, dictionary, primitives, ontology, L8 table -- previously spread over docs/, docs/lithosananke/ and docs/03-architecture/. - docs/working/archive/historical/: finished work (session plan, test-gap audit, birthing plan, fix write-ups, the January architecture draft). - docs/working/archive/superseded/: the Hermes-VM Tripod docs and July Hermes designs (-> FABRIC-3.5/3.6), the StarForth roadmap, every working doc already flagged superseded or obsolete. - docs/working/archive/dead/: the hal_* target contract (never adopted), L4Re, metrics-and-knobs. - Papers and proposals into docs/working/papers/. - References rewritten across the repo (not logs/, not docs/patent/); CLAUDE.md's documentation section rewritten. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SUPERSEDED (docs triage 2026-10-14). The Tripod as Hera/Hermes/Artemis; the Hermes VM was removed (messaging moved into the kernel as kernel-Hermes) and the Tripod is Hera/Artemis/Hestia. Instead: docs/fabric/FABRIC-3.5.md and FABRIC-3.6.md. Moved here from
docs/03-architecture/tripod/README.md.
docs/working/archive/superseded/2026-08-tripod/
Architectural constraints for the three StarForth VMs that make up the Tripod. These documents are binding — read the relevant one in full before touching any Tripod code. Violating the mythological contract they describe is treated as an architectural error, not a style preference.
- TRIPOD.md — The Tripod as a whole: Hera (VM-HERA=0,
governor — spawns/manages/reaps VMs), Hermes (VM-HERMES=1, messenger —
moves events), Artemis (VM-ARTEMIS=2, memory — owns block storage).
Covers capability-based dispatch (no heat-based routing), the CD-TICK
heartbeat, the K≡1.0 compudynamic conservation invariant, the DoE test
fixture's role, and explicit prohibitions (no heat-based VM routing, no
primitives added without instruction, no
BLOCKcalls outside the 0–3071 ramdrive range). - HERMES.md — Hermes VM architecture: the messenger role.
- ARTEMIS.md — Artemis VM architecture: the memory/block- storage role.
All three documents share a non-negotiable constraint: Tripod implementation is StarForth dialect only — no C99 without Captain Bob's explicit written permission for that specific construct.
See also
docs/working/archive/historical/2026-07-birthing/— birthing plan and QEMU acceptance logs for the Hera-spawns-Hermes/Artemis constellation described here.- Project root