admin/LithosAnanake
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update ARTEMIS.md build status to match reality

Browse Source 
The flat-pool storage scope ("Immediate Goal") has been implemented for
some time -- capsules/artemis/init.4th boots live in the Tripod fleet on
every kernel boot -- but the doc still said "do not begin implementation
without explicit instruction from Captain Bob" in two places, and
CLAUDE.md's pointer still said "build-authorization deferred."

.claude/ARTEMIS.md: replaced both stale lines with a dated Build Status
section giving an honest per-criterion accounting rather than a blanket
"done": 4 of 6 acceptance criteria fully confirmed (boot-state detection,
free-map init, fetch/persist, and -- as of the persist-read fix earlier
today -- cross-boot/cross-arch persistence), K-conservation implemented
but not hard-asserted, and the unrecognized-disk halt implemented but
never actually exercised against real unrecognized content. Future
material (zones, USB hot-plug, ACL records, PKI) remains correctly
marked deferred -- unchanged.

.claude/CLAUDE.md: updated the Artemis pointer line so it's consistent
with the above instead of contradicting it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Robert Allan James
2026-08-02 09:15:16 -04:00
co-authored by Claude Sonnet 5
parent 1c1097ec40
commit 3d9664d176
2 changed files with 34 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/ARTEMIS.md
+33 -3
View File
@@ -131,7 +131,37 @@ not remember *heat*. Every join is a cold join.
6. Unrecognized disk content halts the mount with a clear error — no
silent overwrite.
**Do not begin implementation without explicit instruction from Captain Bob.**
### Build Status — Implemented (2026-08-02)
Implementation happened; this section used to say "do not begin without
explicit instruction" — that instruction was given and the work is done
for this scope. `capsules/artemis/init.4th` implements the full flat-pool
target above, and Artemis boots live in the Tripod fleet (announces ready
to Hermes) on every amd64/aarch64/riscv64 kernel boot.
Acceptance criteria status, verified 2026-08-02:
1. ✅ `ART-BOOT-DETECT` — BLANK/LithosAnanke/Unrecognized classification,
confirmed working (both the blank→format and resume paths observed
live in boot logs).
2. ✅ `ART-FORMAT` — free map initializes fresh on BLANK, confirmed.
3. ✅ `BLK-FETCH`/`BLK-PERSIST` — confirmed working against the real
virtio-blk-backed disk image.
4. ⚠️ K is tracked and printed before/after alloc/free
(`ART-K-TOTAL`/`ART-SELF-TEST`), but nothing asserts the before/after
values actually match — implemented, not yet a hard-checked invariant.
5. ✅ Cross-boot AND cross-arch persistence — confirmed via
`ART-WRITE-TEST`/`ART-READ-TEST`, `PASS: persist-read` on all three
architectures against the same disk image (a write on one arch reads
correctly on the other two). Note: `disk/artemis.img` itself had been
silently stuck failing this exact test since before this repo's git
history begins (bad *data* from some pre-history run, not bad code)
until reformatted this same day — see `disk/README.md`.
6. ⬜ `ART-HALT-UNRECOG` exists and looks correct by inspection, but has
not actually been exercised against genuinely unrecognized disk
content — untested, not confirmed.
Not done: everything under "FUTURE MATERIAL" below (zones, USB hot-plug,
ACL records, PKI) — that line remains accurate and unchanged.
---
@@ -163,8 +193,8 @@ compudynamic concerns:
2. Block thermal state — how hot is each active block
3. K≡1.0 — fleet conservation across all block operations
These must be designed together. Do not implement one without the others.
Do not begin implementation without explicit instruction from Captain Bob.
These must be designed together — and were: see Build Status under
Immediate Goal, above, for what's actually implemented and verified.
---
.claude/CLAUDE.md
+1 -1
View File
@@ -10,7 +10,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
> **Tripod:** `.claude/TRIPOD.md` is authoritative for all Tripod VM (Hera/Hermes/Artemis) work. Read it completely before touching any Tripod code.
> **Hermes:** `.claude/HERMES.md` is authoritative for all Hermes VM work. Read before touching Hermes.
> **Artemis:** `.claude/ARTEMIS.md` is authoritative for all Artemis VM work. Read before touching Artemis. Note: Artemis is design-confirmed but **build-authorization deferred** as of this writing — see the "Build Status" section of that file before assuming it's live.
> **Artemis:** `.claude/ARTEMIS.md` is authoritative for all Artemis VM work. Read before touching Artemis. Note: as of 2026-08-02 the flat-pool storage scope ("Immediate Goal" in that file) is **implemented and live** — Artemis boots and manages `disk/artemis.img` in the Tripod fleet on every kernel boot, all three architectures. Zones, USB hot-plug, ACL records, and PKI remain deferred future material — see that file's "Build Status" section for exactly what's verified vs. not.
> **Scope:** This repo is LithosAnanke — the bare-metal UEFI kernel that boots StarForth
> directly on hardware. StarForth (the hosted FORTH-79 VM) has its own separate repository