plans: step 3 §6.2 ruled, both, nucleus first

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:27:31 +00:00
parent 1961348e15
commit 4ecdc80197
@@ -81,6 +81,8 @@ It is a module of its own, so the proofs can state it on its own (ADR step 5).
3. `test_mkf18a`, new: a small text's artifact read back unit by unit against `ARTIFACT.md`. It checks the
magic, the counts, each record, every reserved unit 0, and the code low byte first.
4. `test_host_artifact`: the nucleus, placed from its artifact, equal to the ROM's assembly word for word.
5. Then a small train, a few words of `.f18` with one import from the nucleus, is placed from its artifact
at a base other than 0. Its words run, and its calls into the nucleus reach the nucleus (ruled §6.2).
POST, the protocol and the dictionary gate are unchanged, since the boot is unchanged.
@@ -97,7 +99,9 @@ ADR step 8 asks. The boot gains nothing.
system's source also holds addresses in whole cells: the `&NAME` literals (31 in `capsules/v4/sys`),
and the dictionary's links. One fix is a slot value of 7 meaning "the whole cell". The top 3 bits allow
0–7, so the record keeps its size.
2. **Which train first.** The nucleus is the only `.f18` train, but it is not relocatable, and the ROM keeps
2. ~~Which train first~~ **Ruled 2026-11-19: "Both, nucleus first".** The nucleus is built and checked
against the ROM; then a small train is placed at a base other than 0, to prove the relocations (§4,
test 5). As asked: The nucleus is the only `.f18` train, but it is not relocatable, and the ROM keeps
assembling it (§1). Its artifact can be built and checked (§3), but it is never placed by the loader.
Is the nucleus the first artifact, or is a small relocatable train written first?
3. **The order of the sources.** Captain Bob's image is "the .f18 assembler assembles all .f18 files it