diff --git a/docs/v4.0.0/plans/2026-11-18-v4-init.md b/docs/v4.0.0/plans/2026-11-18-v4-init.md index b4b315b2..3fcbfecf 100644 --- a/docs/v4.0.0/plans/2026-11-18-v4-init.md +++ b/docs/v4.0.0/plans/2026-11-18-v4-init.md @@ -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? 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. 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.**