plans: step 3 §6.4 ruled, every fixed-effect word exported

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:21 +00:00
parent 255dd92deb
commit a6371b1ce3
@@ -40,7 +40,6 @@ A C tool beside `mkrom.c`, built the same way, one per cell width:
- an empty verification record;
- the string pool and the code, low byte first.
3. It fails the build if anything cannot be written as the ABI requires:
- an export with no fixed effect (2c);
- a relocation whose patched address is beyond its slot's reach;
- a capability it cannot derive.
@@ -124,7 +123,9 @@ ADR step 8 asks. The boot gains nothing.
first. One point for its design: the directory holds both widths' maps, `map-32.f18` and `map-64.f18`,
and name order would take both.
4. **Which words are exports.** The nucleus defines hundreds of words, and some have no fixed effect, which
4. ~~Which words are exports~~ **Ruled 2026-11-19: "Every fixed-effect word".** Every word the tool
derives a fixed effect for is exported; the rest stay internal, and the build does not fail for them.
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