Files
LithosAnanake/.claude
Robert Allan JamesandClaude Sonnet 5 72c14cb9eb
Build / build-amd64-iso (push) Waiting to run
Build / build-aarch64-iso (push) Waiting to run
Build / build-riscv64-img (push) Waiting to run
FABRIC-3.md: open new living document (bare metal boot); close FABRIC-2.md
FABRIC-2.md closed/archival as of 2026-09-04 -- its full punch list
(§I) was worked through to completion this session. FABRIC-3.md opens
as the new living document, topic: bare metal boot (FABRIC-2.md §I.6's
own Milestone 8, the one item that couldn't close from a coding
session -- needs a real machine and a human present).

First task written up before executing, per this series' own standing
discipline: merge v2.0.1 into master and verify build/function
equivalence on a clean master tree. Investigated the branch topology
first -- master is a strict ancestor of v2.0.1 (47 commits behind, no
divergent history), so this is a pure fast-forward, not a real merge.

Updated FABRIC-4.md's and .claude/CLAUDE.md's stale pointers at
FABRIC-2.md as "current/living" to point at FABRIC-3.md instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019YcT3H2PQeyujrzjqS3Var
2026-09-04 11:31:04 -04:00
..

.claude/

Project-level configuration and instructions for Claude Code (claude.ai/code) when working in this repository.

  • CLAUDE.md — the authoritative reference for how an AI agent should work in this codebase: hard rules (branch discipline, never work on master without permission, never stash without permission, report bugs rather than fixing them unprompted), build commands for both the hosted VM and the LithosAnanke kernel, architecture summaries, and pointers into the rest of the documentation tree. docs/CLAUDE.md is an older, hosted-only snapshot kept for historical reference — this file supersedes it.
  • TRIPOD.md — architectural constraints for the Tripod: the three-VM fleet (Hera the governor, Hermes the messenger, Artemis the memory/ storage owner) that LithosAnanke boots. Defines each VM's contract and what NOT to put in each one (e.g. no storage logic in Hermes, no event routing in Artemis).
  • HERMES.md — Hermes VM architecture: the message-routing VM. Read in full before touching any Hermes-related code.
  • ARTEMIS.md — Artemis VM architecture: the block-storage/persistence VM, including its free-map allocator. Read in full before touching any Artemis-related code.
  • settings.json — Claude Code session/tooling configuration for this repository.

All four .md files here are binding constraints, not suggestions — they are read in full before any work on the subsystem they cover, per this project's own stated policy.