plan capsule blocks: (- marks a system blob -- the idea, its rulings so far, and what is open

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-18 19:51:40 +00:00
parent f30005e1f6
commit dd3469f9a3
@@ -116,3 +116,37 @@ Each step is test first, then POST and the protocol:
5. **The documents.** The range tables go, and the rules take their place. `experiments/bare_metal/
README.md` rule 3 ("file order") goes.
## 5. `(-` marks a system blob (Captain Bob's idea, 2026-11-18; nothing built)
**The idea, as given:**
- `(-` is a special comment word, terminated by `)` like any `(` comment.
- It also "leaves behind the equivalent of a magic number".
- "The capsule loader can differentiate a 'system capsule' from any other capsule and it can be
diverted into 'please include in a kernel rom image'."
**What exists already:**
- **v3:** `(-` is a C word (`v3/src/word_source/starforth_words.c:274`) that skips to the matching
`)` and nests. Its own comment says it is "used for marking blocks that should be extracted to
init.4th", so v3 already meant it as a marker.
- **v4:** the same nesting comment, in `capsules/v4/physics.4th` block 8204.
- **POST:** v3's 4 cases for it pass in v4.
**Ruled:**
1. **The magic number lives in both places.** `mkcapsule` recognises `(-` at build time, and
interpreting it also leaves the magic number at run time, for the loader to check.
2. **`(-` nests, as now.** Only the magic number is added; the 4 POST cases are unchanged.
3. **It is per named blob** ("Named blobs are well defined in the documents": MACHINE.md §1–2, the
trailer's source, typed by name). Read here as: a blob that opens with `(-` is a system blob, as a
magic number opens a file. Captain Bob to correct this if it is wrong.
4. **Where a system blob goes is open.** "I'm thinking either 3 or 1":
- (1) a new, read-only kernel ROM image holding the system blobs only;
- (3) the kernel's capsule directory holding the system blobs only, with every other blob loaded
from elsewhere (Artemis, the stick).
Not (2), v4's node ROM.
**Still to settle before any of it is built:**
- the choice between (1) and (3);
- what the run-time magic number is (a variable's value, or a cell the loader reads);
- what the loader does with an unmarked blob in each case.