plans: step 3 §6.5 ruled, the tool's hash is its source's

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 16:32:59 +00:00
parent 3733949c28
commit 6c639e5d20
@@ -128,7 +128,9 @@ ADR step 8 asks. The boot gains nothing.
As asked: The nucleus defines hundreds of words, and some have no fixed effect, which
2c refuses as exports. Is every word with a fixed effect exported, or only those a list names? With a
list, the words outside it stay internal.
5. **The tool's identity.** The provenance holds "the host tool's hash". The hash of the binary differs
5. ~~The tool's identity~~ **Ruled 2026-11-19: "Its source".** The provenance's tool hash is the SHA-512 of
the tool's source: `mkf18a.c`, `text.c`, `effect.c` and the v4 headers they include, in a fixed order.
The same source gives the same hash on every host. As asked: The provenance holds "the host tool's hash". The hash of the binary differs
with the host's compiler. Should it be the hash of the tool's source (`mkf18a.c`, `text.c`, `effect.c`
and their headers), or of the binary?
6. **The name.** `mkf18a` and `.f18a`, after the magic, or something else?