From 3b229ba6355dc163847d840566c4253f2337d5b8 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 19 Nov 2026 14:51:31 +0000 Subject: [PATCH] ABI choice 3: the engine carries its source by reference (its hash), not as a car Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm --- docs/v4.0.0/ABI.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/v4.0.0/ABI.md b/docs/v4.0.0/ABI.md index 2a50ccc3..7b676ebe 100644 --- a/docs/v4.0.0/ABI.md +++ b/docs/v4.0.0/ABI.md @@ -147,7 +147,10 @@ stock." Ruled "One train per capsule" (§1). leaving a count of values, branches that leave different depths, `EXECUTE`, a `DEFER`red word) has no fixed count. It cannot be exported by an engine: it stays internal to its train, or is restructured. Every export has a fixed effect, which the tool derives and the build fails without. -3. **What a capsule carries:** an artifact alone, or the artifact and its source (provenance, ADR §3.1)? +3. ~~What a capsule carries~~ **Ruled 2026-11-19: "No, by reference".** A train's engine carries only the + hash of the `.f18` source it was assembled from, in its provenance record. The source stays in the + repository and in its own capsule. To check an engine against its source, the source is fetched by + that hash. 4. **Imports by capsule hash:** a hash pins one exact build. Is an import of an older build of the same capsule a mismatch, or is the name of the capsule enough with the stack effect checked? 5. **How callers reach a replacement:**