plans: task 4 ruled -- host placer in C, it lays entries, the tool assembles the nucleus, import nucleus NAME

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-20 03:46:54 +00:00
parent 7422dc5319
commit 3945d3964a
@@ -321,14 +321,17 @@ and placing them on a node are the ADR's steps 4 and 6 (§3).
5. Refusals, each leaving the node unchanged: a nucleus import the dictionary lacks; an import whose 5. Refusals, each leaving the node unchanged: a nucleus import the dictionary lacks; an import whose
effect disagrees; an artifact the checker refuses; a relocation out of its slot's reach at that base. effect disagrees; an artifact the checker refuses; a relocation out of its slot's reach at that base.
**For ruling, one at a time:** **Ruled 2026-11-20, one at a time:**
1. **Where placement runs in task 4.** (a) A host placer in C, `v4/src/place.c`, writing the node's 1. **Placement: "Host placer in C".** `v4/src/place.c` checks, copies, patches and enters into a host
memory. That is the oracle for the loader on the node, later. (b) The loader in FORTH on the node now, node's memory, in the booted host system. It is the oracle for the loader on the node (step 6). Asked:
pulled forward from step 6. a host placer in C, or the loader in FORTH on the node now, pulled forward from step 6.
2. **How the exports are entered.** (a) The placer lays each entry as `(HEADER)` lays one (`ABI.md` §5, 2. **Entries: "Placer lays entries".** The placer lays each export's entry as `(HEADER)` lays one: the ID,
step 4), and the kernel is told, as `(WORD-DEFINED)`. (b) No entries in task 4: the test calls the the flags with the ACL defaults, the name, the link, the code. It tells the kernel, as `(WORD-DEFINED)`
words by address, and entering is left to step 6. does. The test runs the words by name at the console. Asked: entries now, or calls by address and
3. **How the tool knows the nucleus's effects.** (a) It assembles the nucleus itself, `capsules/v4/sys` entries left to step 6.
with its map, and derives each header's effect, as task 2's measurement did. A new argument names 3. **The nucleus's effects: "Tool assembles it".** `mkf18a` is given the nucleus's directory, assembles it
the directory. (b) A file of the nucleus's effects is generated once per build and given to the tool. with its map, and derives each header's effect by name, as task 2's measurement did. Nothing is
4. **How an import names the nucleus.** `import nucleus NAME`, with `nucleus` a reserved train name. generated in between. Asked: that, or an effects file generated once per build.
4. **The import's name: "import nucleus NAME".** `nucleus` is a reserved train name: the import has hash
0, its effect from the nucleus, and placement resolves it by name in the dictionary. Asked: that, or a
directive of its own.