plan capsule blocks: land at n, copy down to n-R; where it lands is the developer's responsibility

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 17:24:16 +00:00
parent 5210abaa4e
commit 47712e0cd1
@@ -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.