Files
LithosAnanke/docs/v4.0.0/plans/2026-11-19-f18-artifacts.md
T
Claude 4f7521290a
Build / Image RASPI (push) Successful in 3m42s
Build / Image MILKV (push) Successful in 3m58s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 13m55s
Build / Image PC (push) Successful in 3m57s
ADR rulings 4: a word's logical identity is its capsule (content hash) + its name
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:37:55 +00:00

27 lines
2.0 KiB
Markdown

# F18 binary artifacts, ABI/API, live updates -- the rulings
The decision is `docs/v4.0.0/ADR-2026-11-19-F18-ARTIFACTS.md`, recorded as given. This file records each
conflict between it and the existing record, put to Captain Bob one at a time, and his ruling.
**Nothing is built.** The ADR's §7 order is followed; step 1 is the minimal ABI contract.
## The conflicts, one at a time
1. **"The ROM is the only binary"** (MACHINE.md §1, §5, ruled 2026-10-15) against compiled F18 artifacts.
**Ruled: "ADR supersedes".** MACHINE.md §1 and §5 now say that compiled artifacts are allowed beside the
ROM. An artifact is a choice, not a requirement: the ROM still assembles source at boot.
2. **"Hermes: Messaging, routing, and communication"** (ADR §3.3) against the record. The Hermes VM was
removed (FABRIC-3.5/3.6, 2026-09-22), and v4's messages travel on the fabric's wires and routes.
**Ruled: "The messaging role".** Hermes names the role, not a VM: in v4 the fabric's wires and routing,
and on v3 kernel-Hermes. No Hermes node is brought back. The ADR carries a note saying so.
3. **"Artemis: Memory, persistence, and recovery"** (ADR §3.3) against the record. Artemis is the persistence
path (FABRIC-3.5 XIV.3), and memory is the kernel's. **Ruled: "Persistent memory".** Artemis owns what is
kept: persistent storage, staged artifacts and recovery copies. Run-time memory stays the kernel's: the
Stadium allocates it, and the kernel serves blocks. The ADR carries a note saying so.
4. **A word's logical identity** (ADR §3.2: not addresses or placement). Today v4 has three identities: the
word ID (assigned in order, given back by FORGET), `ACL-WORD-ID` (its address) and the kernel's table of
entries (addresses). **Ruled: "Capsule + name".** A word's identity is its defining artifact's identity,
the content hash, plus the word's name. It is stable across builds of the same source and independent of
where the word loads. Addresses and word IDs stay as local resolution only.