ABI choice 3: the engine carries its source by reference (its hash), not as a car
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
+4
-1
@@ -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:**
|
||||
|
||||
Reference in New Issue
Block a user