ABI choice 4: imports name the exact build (capsule hash); an update replaces the dependent set together

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
Claude
2026-11-19 14:51:53 +00:00
parent 3b229ba635
commit bc876f8088
+4 -2
View File
@@ -151,8 +151,10 @@ stock." Ruled "One train per capsule" (§1).
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?
4. ~~Imports by capsule hash~~ **Ruled 2026-11-19: "Exact hash".** An import names the exact build of
the train it imports from: (its capsule hash, the word's name). If that train is rebuilt or updated,
its hash changes, so its importers are rebuilt too, and a live update replaces the whole dependent set
of trains together. Placement refuses an import whose hash is not present.
5. **How callers reach a replacement:**
- (a) the old entry's code is overwritten by a `jump` to the new: one cell, every caller follows, and the
old code is unreachable but for that cell;