diff --git a/docs/v4.0.0/plans/2026-11-19-f18-artifact-build.md b/docs/v4.0.0/plans/2026-11-19-f18-artifact-build.md index 38ef09af..25d83a12 100644 --- a/docs/v4.0.0/plans/2026-11-19-f18-artifact-build.md +++ b/docs/v4.0.0/plans/2026-11-19-f18-artifact-build.md @@ -61,9 +61,10 @@ It is a module of its own, so the proofs can state it on its own (ADR step 5). - **`v4/Makefile`:** `make -C v4 artifacts` builds the artifacts of each width into `v4/build/`. `make -C v4 test` runs it, so a `.f18` the tool refuses fails the test gate. -- **The check against the ROM:** a new test, `test_host_artifact`, places the nucleus's artifact on node A at - its own origin, by the relocation records. Node B is the ROM assembling the same source. Every word must - agree, as `test_host_rom_nucleus` checks now. That proves the records, as well as the assembler. +- **The check against the ROM:** the nucleus is not an artifact (ruled §6.2a), so no file is written for it. + `test_host_rom_nucleus` assembles it with the tool's assembler, the address record turned on, and the ROM + must still lay down every word the same. That proves the record changes no cell. The records themselves + are proved by the small train (§4, test 5). - **The kernel build:** nothing changes in step 3. The boot still feeds the ROM the source. Carrying the artifact in the capsule, and placing it, is steps 4 and 6. - **CI:** `build.yml`'s `v4-tests` job runs `make -C v4 test` already, so it gains the gate with no change. @@ -80,7 +81,8 @@ It is a module of its own, so the proofs can state it on its own (ADR step 5). - two branches that disagree (no fixed effect). 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. +4. `test_host_rom_nucleus`, with the address record on: the ROM's assembly equal to the tool's, word for + word (ruled §6.2a: no artifact file for the nucleus). 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). @@ -103,6 +105,11 @@ ADR step 8 asks. The boot gains nothing. 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. + + **2a, ruled 2026-11-19: "Nucleus not an artifact".** Asked how an artifact would say it is fixed at an + origin, since `ABI.md` §4 has its code "as if placed at address 0": only relocatable trains are + artifacts. The nucleus is checked as the tool's assembly against the ROM's, and no artifact file is + written for it. `ABI.md` §4 stands. 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 finds", but the order matters: the map first, `sys_files.h`'s list, `end.f18` last. Does each train