plan capsule blocks: collisions overwrite -- "Deterministic and final" (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 17:21:15 +00:00
parent 38c4d5ac69
commit 1061433791
@@ -41,9 +41,10 @@ Written 2026-11-18, from the capsules talk with Captain Bob. It records the ruli
## 3. Open, one at a time
1. ~~The `Block <n>` header~~: ruled above.
2. **The collision check across capsules.** If each capsule is loaded, relocated, interpreted and
then freed before the next, two capsules may use the same numbers. Does the check go, or is it
kept for capsules that are resident together?
2. ~~The collision check across capsules~~ **Ruled: "Overwrite. That's it. Deterministic and
final."** A page written to a block number already in use overwrites it; what was there is gone.
Which write wins follows from the load order, which is fixed, so it is deterministic. A shared
number is not an error, so `mkcapsule`'s cross-capsule collision check (`:846-879`) goes.
3. **The knobs:** which ones set the offset (where the VM's RAM ends), for v3 and for v4. v4's node
has its own block window (`V4_BLOCK_SLOTS`).
4. **Where the pages land before relocation:** in the kernel's block store at `n`, or straight into