plan v4 init.4th: step 1 first; held -- "Capsules are ephemeral. We need to talk later" (Captain Bob)

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 09:42:04 +00:00
parent a98baaacdd
commit b80bd5cd27
+13
View File
@@ -75,3 +75,16 @@ the system capsules. It is the only boot policy, so the loader's one fixed step
4. `CAPSULE-BIRTH`: v4 has no such word. Is it pinned once it exists, or dropped? 4. `CAPSULE-BIRTH`: v4 has no such word. Is it pinned once it exists, or dropped?
5. Which nodes `init.4th` births at boot, and in what order. 5. Which nodes `init.4th` births at boot, and in what order.
6. Step 4: when the identity gate and the prompt move from C into `init.4th`. 6. Step 4: when the identity gate and the prompt move from C into `init.4th`.
## 6. Rulings so far (2026-11-18)
1. **Step 1 first** (the search order), each step accepted before the next.
2. **Held.** Asked where `init.4th`'s blocks go, Captain Bob answered: "It shouldn't matter. Capsules
should not occupy fixed ranges." Then: "Capsules are ephemeral. We need to talk later." This runs
against the tree as it is:
- every capsule's `Block NNNN` headers;
- `mkcapsule`'s check of them;
- the ranges in `BLOCK_MAP.md` and `experiments/bare_metal/README.md`.
It may also change what `init.4th` is: a capsule, or not. **Nothing of this design is built until
that conversation.**