From 73068728485e15d02d585a17d6395c7667aeb4f4 Mon Sep 17 00:00:00 2001 From: Robert Allan James Date: Tue, 22 Sep 2026 19:53:57 -0400 Subject: [PATCH] Phase 5.7: archival close of FABRIC-3.5.md and FABRIC-3.6.md at v2.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit FABRIC-3.5.md's provisional "design phase closed, not yet archival" header replaced with the real CLOSED/ARCHIVAL form per its own §XXVI.5 spec, naming v2.1.0 -- prior status headers kept underneath, not deleted. FABRIC-3.6.md gets the same treatment: a CLOSED/ARCHIVAL banner above the START HERE section, which stays as historical record rather than being removed. Neither closure triggers the FABRIC-0 -> -1 -> -2 -> -3 carry-forward chain (both are standalone topic documents) and neither touches FABRIC-3.md, which remains open for its own topic. The Tripod/kernel reshuffle is complete: Hermes moved into the kernel as kernel-Hermes, the Tripod is Hera/Artemis/Hestia, tagged v2.1.0. Co-Authored-By: Claude Sonnet 5 --- FABRIC-3.5.md | 51 ++++++++++++++++++++------------------------------- FABRIC-3.6.md | 45 +++++++++++++++++++++++++++++++++++++++++---- 2 files changed, 61 insertions(+), 35 deletions(-) diff --git a/FABRIC-3.5.md b/FABRIC-3.5.md index 2959e3ee..3b047e31 100644 --- a/FABRIC-3.5.md +++ b/FABRIC-3.5.md @@ -1,37 +1,26 @@ # FABRIC-3.5.md — the Tripod/kernel reshuffle -**Status: REOPENED 2026-09-19, by direct instruction ("reopen 3.5 and write it up as a gap -analysis section"), to add §XXXI — a gap-analysis sweep of the whole FABRIC set. The design -phase remains closed; §XXXI adds findings, not new design.** +**Status: CLOSED/ARCHIVAL as of 2026-09-22, at tag `v2.1.0`.** Per §XXVI.5's own close +condition ("this document closes when the tag exists"). Produced the full design ruling for +the Tripod/kernel reshuffle: Hermes moves from a FORTH VM into the kernel as kernel-Hermes; the +Tripod becomes Hera/Artemis/Hestia; every design question this document opened is ruled (§XXX.7 +/ §XLI's punch list). Execution against that design is recorded in `FABRIC-3.6.md`, not here — +all five phases (0–5) closed there, ending in the `v2.1.0` tag this header names. **Nothing is +carried forward and no successor is created** — this document is not part of the +`FABRIC-0 → -1 → -2 → -3` chain (§XXVI.5), so closing it hands nothing to a successor. +**`FABRIC-3.md` remains open, living and authoritative for its own topic** (bare metal boot); +nothing here ever superseded it. -> **Prior status, kept rather than overwritten: DESIGN PHASE CLOSED as of 2026-09-19, by -> direct instruction ("close the document for now"). Not yet archival.** That close stood for -> the duration of the sweep and its substance is unchanged — every design question was and -> remains ruled. The reopen is recorded rather than the close deleted, per this series' own -> rule against silently rewriting a prior state. - -**What is closed, and what is deliberately not.** Every design question this document opened is -ruled — see §XXX.7. **No code has been written and no code is authorized.** The execution -sequence (§XXVI.6, as amended by §XXX.7) is untouched: the surgical strip, the build, the -Isabelle/HOL pass, the documentation sweep, the SBOM, the merge to `master`, and the `v2.1.0` -tag all remain ahead. - -**This is therefore a narrower close than §XXVI.5 specified**, and the difference is stated -rather than glossed. §XXVI.5 ruled that this document closes *when the tag exists*, in -`FABRIC-2.md`'s CLOSED/ARCHIVAL form, naming the tag it closed at. **The tag does not exist**, -so claiming that close would be a label running ahead of the real state — the exact error -`FABRIC-3.md` §I.2 corrected when it rolled `LITHOS_VERSION` back, and the same standard §XXIX -applied to the LTS question. **The archival close specified by §XXVI.5 still stands and still -happens at `v2.1.0`.** This header is the provisional one the instruction's own "for now" asks -for. - -**Nothing is carried forward and no successor is created.** As §XXVI.5 establishes, this -document is not part of the `FABRIC-0 → -1 → -2 → -3` chain, so closing it hands nothing to a -successor. **`FABRIC-3.md` remains open, living and authoritative for its own topic** (bare -metal boot); nothing here supersedes it. The live artifact from this document is its punch list -(§XXVI.6 / §XXX.7) — that, not this header, is what the build works from. - -**Open by design, not by omission:** items 10–17 of §XXVI.6 are execution, not decisions. +> **Prior status headers, kept rather than overwritten, per this series' own rule against +> silently rewriting a prior state:** +> +> **REOPENED 2026-09-19**, by direct instruction ("reopen 3.5 and write it up as a gap analysis +> section"), to add §XXXI — a gap-analysis sweep of the whole FABRIC set. +> +> **DESIGN PHASE CLOSED as of 2026-09-19**, by direct instruction ("close the document for +> now"). Not yet archival at that point — the execution sequence (surgical strip, build, +> Isabelle pass, doc sweep, SBOM, merge, tag) was still entirely ahead. That gap is now closed: +> `FABRIC-3.6.md`'s Phases 0–5 are the execution this header once described as pending. Three things recorded here are explicitly *outside* this reshuffle and still need their own authorization — the `.claude/CLAUDE.md`/`MANIFEST.md` documentation reconciliation (§XXVI.1), the `src/*.c.bak` hygiene question (§XXII.5), and the stray `refs/heads/v2.0.1` branch and diff --git a/FABRIC-3.6.md b/FABRIC-3.6.md index 7ac4a530..4409bddc 100644 --- a/FABRIC-3.6.md +++ b/FABRIC-3.6.md @@ -1,6 +1,24 @@ # FABRIC-3.6.md — the Tripod/kernel reshuffle: execution log -> ## START HERE — session handoff +**Status: CLOSED/ARCHIVAL as of 2026-09-22, at tag `v2.1.0`.** All five phases (0–5) closed — +Category A strip, Hestia relocation/birth, kernel-Hermes build (allocator, arena, message +types), Stage-cutover of every FORTH-owned message type, the Category B strip (Hermes VM + +`messaging.4th` removed), the Isabelle pass, the documentation sweep, `make sbom`, the version +bump, and the merge to `master` + tag. **This document is closed; the reshuffle it tracked is +done, not merely planned.** Per §XXVI.5 (cited here, ruled in `FABRIC-3.5.md`, also closed at +this same tag): closing this document hands nothing to a successor and does not touch +`FABRIC-3.md`, which remains open and authoritative for its own topic (bare metal boot). + +**The `START HERE` section immediately below is kept as historical record of how this +execution began — it describes a session about to start work, not the current state.** Do not +follow its "first action: task 0.0" instruction; every task it points at is closed. If future +work touches this fleet again (a Phase 8 PKI elevation entrypoint, further hardware bring-up, +etc.), it gets its own new document, not a reopening of this one — matching the discipline +`FABRIC-3.5.md`'s own close just followed. + +--- + +> ## START HERE — session handoff (historical — reshuffle complete, see status above) > > **If you have just been told "go build it", read this section, then `FABRIC-3.5.md`'s §XLI, > then start at task 0.0 below. Do not re-derive the design — it is settled.** @@ -1345,7 +1363,7 @@ intermediate states. build its own entrypoint rather than resuming `SEND-ELEVATE-REQUEST`. No further action this phase. -## Phase 5 — Close-out +## Phase 5 — Close-out — **COMPLETE, tag `v2.1.0` cut 2026-09-22** **Note on commit granularity:** tasks 5.1–5.4 landed as one commit (`a4ad14a`), a deliberate deviation from the per-task-commit discipline this document has otherwise used since Phase 0. @@ -1511,8 +1529,27 @@ opposite of what per-task commits are for. Tasks 5.5–5.7 return to one-commit- closed `2026-09-18T21:28:26Z` — 20 seconds later, before any of this reshuffle's actual work existed on the branch. Already closed, already not merged, blocks nothing. Nothing to resolve beyond recording what it is. -- [ ] **5.6** — Merge to `master`; tag `v2.1.0`. -- [ ] **5.7** — Archival close of `FABRIC-3.5.md` (§XXVI.5) and of this document. +- [x] **5.6** — Merge to `master`; tag `v2.1.0`. + 2026-09-22 · **Closed, explicit approval obtained first (this is a shared-branch + operation on the sole production line — the plan authorizing it is not a standing + grant, per `.claude/CLAUDE.md`'s own scope rule).** `master` was a strict ancestor of + this branch (`git merge-base --is-ancestor origin/master HEAD` — true, 0 commits unique + to `master`, 85 unique to this branch), so this was a clean fast-forward, not a merge + commit: `git push origin HEAD:refs/heads/master` (`e56974e..8edbd3c`), never checking out + `master` locally, so the uncommitted `FABRIC-3.md` WIP on this branch's working tree was + never touched. Tagged `v2.1.0` (annotated, `8edbd3c`) and pushed. `refs/heads/v2.0.1` + (task 5.5's finding — fully merged, safe to delete) also deleted this same pass, explicit + approval obtained first. +- [x] **5.7** — Archival close of `FABRIC-3.5.md` (§XXVI.5) and of this document. + 2026-09-22 · **Closed.** `FABRIC-3.5.md`'s provisional "design phase closed, not yet + archival" header replaced with the real CLOSED/ARCHIVAL form, naming `v2.1.0`, per its + own §XXVI.5 spec — prior status headers kept underneath, not deleted, matching this + series' own no-silent-rewrite rule. This document (`FABRIC-3.6.md`) closed the same way: + a CLOSED/ARCHIVAL status banner added above the `START HERE` section, which is kept as + historical record of how the session began rather than removed. Neither closure triggers + the `FABRIC-0 → -1 → -2 → -3` carry-forward chain (both documents are standalone topic + documents, not part of it) and neither touches `FABRIC-3.md`, which stays open for its + own topic. **Phase 5, and the Tripod/kernel reshuffle itself, are complete.** ---