Rename FABRIC series: FABRIC.md->0, FABRIC-2.md->1, FABRIC-3.md->2, FABRIC-4.md unchanged

FABRIC.md -> FABRIC-0.md FABRIC-2.md -> FABRIC-1.md FABRIC-3.md -> FABRIC-2.md (the current/living document) FABRIC-4.md unchanged (new #3 to follow separately) Every cross-reference repo-wide updated to match, including doc-comment citations inside kernel source (.c/.h) files -- done via an ordered placeholder substitution (FABRIC-3.md->placeholder2, FABRIC-2.md-> placeholder1, FABRIC.md->placeholder0, then placeholders resolved to final names) in a single pass per file to avoid double-shifting already-renamed references. One line in capsules/font.4th grew past the 64-char block-format limit as a side effect of the longer filename; shortened it and reverified with mkcapsule --lint (34/34 pass) before rebuilding. Verified 3-arch boot to ok> (amd64/aarch64/riscv64, each in the foreground) after the fix; logs and DoE CSVs from this session's verification runs included per this repo's own audit-artifact convention. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019YcT3H2PQeyujrzjqS3Var
2026-09-04 11:22:51 -04:00
parent ff2941dfb9
commit b031b802e3
128 changed files with 37154 additions and 9572 deletions
@@ -5,11 +5,11 @@
 ---

 > **SUPERSEDED (Captain Bob, 2026-08-15).** This document is no longer authoritative.
-> `FABRIC.md`/`FABRIC-2.md` (repo root — read `FABRIC-2.md` first, it is the current/living
+> `FABRIC-0.md`/`FABRIC-1.md` (repo root — read `FABRIC-1.md` first, it is the current/living
 > one) are the sole design-of-record for Artemis work now. Kept here as historical record
 > only; do not read this for current design authority, and do not cite it in place of
-> `FABRIC.md`/`FABRIC-2.md`. Artemis becoming the pre-Artemis-closeout blocker (item 4.6) is
-> tracked in `FABRIC-2.md`, not here. See `.claude/CLAUDE.md`'s own pointer.
+> `FABRIC-0.md`/`FABRIC-1.md`. Artemis becoming the pre-Artemis-closeout blocker (item 4.6) is
+> tracked in `FABRIC-1.md`, not here. See `.claude/CLAUDE.md`'s own pointer.

 ---

@@ -148,7 +148,7 @@ for this scope. `capsules/artemis/init.4th` implements the full flat-pool
 target above.

 **Corrected 2026-08-13 — the "boots live in the Tripod fleet... on every
-kernel boot" claim below is stale since item 0.1 (`FABRIC.md` Phase 0),
+kernel boot" claim below is stale since item 0.1 (`FABRIC-0.md` Phase 0),
 same pattern already found and fixed in `TRIPOD.md`.** Two distinct things
 were being conflated: Artemis's block-storage *device* (the virtio-blk
 disk, `disk/artemis.img`) genuinely does auto-attach at the C level at
@@ -10,12 +10,12 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co

 > **Superseded subsystem docs (Captain Bob, 2026-08-15):** `.claude/TRIPOD.md`,
 > `.claude/HERMES.md`, `.claude/ARTEMIS.md`, and `.claude/CONSOLE.md` are all superseded —
-> `FABRIC.md` and `FABRIC-2.md` (both design history/archival as of 2026-08-25) and
-> `FABRIC-3.md` (current/living, read this one first) are the sole authoritative source for
+> `FABRIC-0.md` and `FABRIC-1.md` (both design history/archival as of 2026-08-25) and
+> `FABRIC-2.md` (current/living, read this one first) are the sole authoritative source for
 > Tripod/Hermes/Artemis/Console work now. The four subsystem docs remain in the repo as
 > historical record only; each carries its own superseded-header pointing here. Do not treat
 > them as current, do not read them for design authority, and do not cite them in place of
-> `FABRIC.md`/`FABRIC-2.md`/`FABRIC-3.md`.
+> `FABRIC-0.md`/`FABRIC-1.md`/`FABRIC-2.md`.

 > **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
@@ -133,14 +133,14 @@ The word-level ACL system is fully implemented, including kernel parity. Key con
 - Measured overhead: +0.0054%–+0.0088% across all 9 cells; CV = 0.000%
 - Report confirmed to exist: `experiments/bare_metal/analysis/report/bare_metal_doe_report.pdf`
  (~2MB, with LaTeX source and figures) — patent support material
- **Correction (found 2026-08-20/21, `FABRIC-2.md` §§M–T):** the "ACL-RWT" name itself was
+- **Correction (found 2026-08-20/21, `FABRIC-1.md` §§M–T):** the "ACL-RWT" name itself was
  wrong — the Rolling-Window-of-Truth mechanism it was named after was dead code, removed
  2026-07-08 (`ACL-RECHECK-RW` was never reachable — `acl_recheck()` only ever looks up the
  11-char `ACL-RECHECK`, never the 14-char `-RW` variant). What this campaign actually
  measured was the live `ACL-TTL` mechanism under a misleading name, and at `-O0`, before
  real compiler optimization landed. The corrected, current figure — same live mechanism,
  correct name, re-run on the current substrate — is **+0.0603% ACL-TTL enforcement overhead,
-  architecture-independent, CV=0.000%** (`FABRIC-2.md` §T, memory
+  architecture-independent, CV=0.000%** (`FABRIC-1.md` §T, memory
  `project_acl_ttl_overhead_final.md`). Use that number, not the one above.

 **Before writing or modifying any `.4th` capsule file**, read `experiments/bare_metal/README.md`
@@ -20,11 +20,11 @@

 > **SUPERSEDED (Captain Bob, 2026-08-15).** This document is no longer authoritative, and its
 > core premise below ("Console is a 4th Tripod VM, Quadrupod, StarForth-dialect-only") was
-> architecturally reversed by a later, decided ruling: `FABRIC.md` §17.5 — the framebuffer is
+> architecturally reversed by a later, decided ruling: `FABRIC-0.md` §17.5 — the framebuffer is
 > a **utility**, not a patron, not a VM. What actually shipped is direct C
 > (`src/starkernel/hal/console.c`/`vt100.c`/`framebuffer.c` plus keyboard drivers), called
-> straight from the kernel, no Hera-spawned Console VM anywhere. `FABRIC.md`/`FABRIC-2.md`
-> (repo root — read `FABRIC-2.md` first) are the sole design-of-record for Console/framebuffer
+> straight from the kernel, no Hera-spawned Console VM anywhere. `FABRIC-0.md`/`FABRIC-1.md`
+> (repo root — read `FABRIC-1.md` first) are the sole design-of-record for Console/framebuffer
 > work now. Kept here as historical record only. See `.claude/CLAUDE.md`'s own pointer.

 ---
@@ -5,10 +5,10 @@
 ---

 > **SUPERSEDED (Captain Bob, 2026-08-15).** This document is no longer authoritative.
-> `FABRIC.md`/`FABRIC-2.md` (repo root — read `FABRIC-2.md` first, it is the current/living
+> `FABRIC-0.md`/`FABRIC-1.md` (repo root — read `FABRIC-1.md` first, it is the current/living
 > one) are the sole design-of-record for Hermes work now. Kept here as historical record
 > only — note its message-layout table (8 cells) is confirmed stale against the real shipped
-> capsule (9 cells, `capsules/hermes/init.4th`), see `FABRIC-2.md`. Do not read this for
+> capsule (9 cells, `capsules/hermes/init.4th`), see `FABRIC-1.md`. Do not read this for
 > current design authority. See `.claude/CLAUDE.md`'s own pointer.

 ---
@@ -5,10 +5,10 @@
 ---

 > **SUPERSEDED (Captain Bob, 2026-08-15).** This document is no longer authoritative.
-> `FABRIC.md`/`FABRIC-2.md` (repo root — read `FABRIC-2.md` first, it is the current/living
+> `FABRIC-0.md`/`FABRIC-1.md` (repo root — read `FABRIC-1.md` first, it is the current/living
 > one) are the sole design-of-record for Tripod work now. Kept here as historical record
 > only; do not read this for current design authority, and do not cite it in place of
-> `FABRIC.md`/`FABRIC-2.md`. See `.claude/CLAUDE.md`'s own pointer.
+> `FABRIC-0.md`/`FABRIC-1.md`. See `.claude/CLAUDE.md`'s own pointer.

 ---

@@ -35,8 +35,8 @@ or work execution logic in Hera — stop. You have the wrong VM.

 ## The Immediate Goal

-**Corrected 2026-08-13 — stale since item 0.1 (`FABRIC.md` Phase 0), flagged in
-`FABRIC-2.md` §A item 5.3, never fixed until now.** This section used to say Hera spawns
+**Corrected 2026-08-13 — stale since item 0.1 (`FABRIC-0.md` Phase 0), flagged in
+`FABRIC-1.md` §A item 5.3, never fixed until now.** This section used to say Hera spawns
 Hermes and Artemis automatically at boot. She does not, by deliberate design: item 0.1
 pruned `capsules/init.4th` to boot Hera alone (confirmed current —
 `capsules/init.4th` births no other VM). Hermes and Artemis-as-VM-patron births happen