plans, ABI.md: task 3 ruling, a train's hash is its .f18a's capsule ID

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 19:47:39 +00:00
parent 57f556e645
commit cad8291478
2 changed files with 8 additions and 0 deletions
@@ -236,3 +236,8 @@ this is a measure of the analysis, not an interface.
3. **Imports: "An import line"** (2026-11-19). `import TRAIN NAME` declares NAME as from the train TRAIN,
before it is used. The tool takes TRAIN's capsule hash, and the word's derived effects, from that train's
build, so the build fails if TRAIN does not export NAME. Each call to NAME is a relocation to its import.
4. **A train's capsule hash: "Its .f18a's capsule ID"** (2026-11-19). A train is identified by its engine:
the capsule ID `mkcapsule` gives its `.f18a`. The nucleus has none (§6.2a), so a word imported from it
is named with hash 0 and resolved by name in the node's dictionary at placement. Exact-hash imports
(`ABI.md` choice 4) hold between artifact trains only. Asked because a capsule today is one file, and
the nucleus is 16 blobs.