diff --git a/docs/v4.0.0/plans/2026-11-18-capsule-blocks.md b/docs/v4.0.0/plans/2026-11-18-capsule-blocks.md index 63157326..4c6e6bfd 100644 --- a/docs/v4.0.0/plans/2026-11-18-capsule-blocks.md +++ b/docs/v4.0.0/plans/2026-11-18-capsule-blocks.md @@ -52,6 +52,12 @@ Written 2026-11-18, from the capsules talk with Captain Bob. It records the ruli - `mkcapsule` is given it at build time in place of its literal 2048 (`:414`, `:1094`). v4's node window (`V4_BLOCK_SLOTS`) is not the source of the offset. -4. **Where the pages land before relocation:** in the kernel's block store at `n`, or straight into - the relocated slot. +4. ~~Where the pages land~~ **Ruled: at `n`, then copied down.** + - Each page is written to the block store at `n`, then copied to `n - R` for interpreting, where + R is the RAM block count (ruling 3). + - Block `n` is then free again. + - Asked about pages whose `n - R` falls outside the RAM (`Block 4096` lands at 2048 when R is + 2048), Captain Bob ruled: **"Just copy down the specified blocks. Where they land will be + developers responsibility."** The loader does not check where a page lands. The one rule left + is that `n` is at least R (`mkcapsule`'s floor, from the knob). 5. **The range tables and `BLOCK_MAP.md`:** go, or become a record of what each capsule uses.