diff --git a/.claude/ARTEMIS.md b/.claude/ARTEMIS.md
index 712627e..d2359f5 100644
--- a/.claude/ARTEMIS.md
+++ b/.claude/ARTEMIS.md
@@ -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.
 
 ---
 
diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
index c49f711..efbda35 100644
--- a/.claude/CLAUDE.md
+++ b/.claude/CLAUDE.md
@@ -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