From cda8aad8b26381029082d6b7f300447d0ea7ff07 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 18 Nov 2026 17:26:22 +0000 Subject: [PATCH] plan capsule blocks: no chaining, developer responsible; the work, for ruling Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm --- .../v4.0.0/plans/2026-11-18-capsule-blocks.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) 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 c01d0ceb..8b7b04e4 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 @@ -70,4 +70,29 @@ Written 2026-11-18, from the capsules talk with Captain Bob. It records the ruli 6. **Chaining.** Under "the lowest block first; the current block determines the next", only a capsule's lowest page runs unless it chains. No capsule in the tree chains its pages today (`forth79.4th` has 3 pages, `centre.4th` 7, v3's `init.4th` 3, none with `-->`, `LOAD` or - `THRU`). Open: awaiting Captain Bob's answer. + `THRU`). **Ruled: "No 'chaining' again developer responsible."** + - The loader interprets the capsule's lowest page and nothing more. + - A capsule that needs its other pages chains them itself (`-->`, `LOAD`, `THRU`). + - So each capsule in the tree is given its chaining when the loader changes, or only its lowest + page would run. + +## 4. The work, for ruling (nothing built) + +Each step is test first, then POST and the protocol: +1. **The knob.** The RAM block count becomes a Kconfig symbol. `block_subsystem.h` and the kernel read + it, and `mkcapsule` is given it at build time in place of its literal 2048. +2. **`mkcapsule`.** + - Its floor comes from the knob. + - Its cross-capsule collision check goes, since a later write overwrites. + - `BLOCK_MAP.md` says "Blocks used". + - Open: whether a number repeated within one capsule is still refused, or overwrites by the same + rule. +3. **The capsules chain their own pages.** Each multi-page capsule ends each page with `-->`, or has + its lowest page `THRU` the rest. That keeps it working under step 4. +4. **The loaders,** v4's `load()` and v3's `INIT`: + - each page is written to block `n`, then copied down to `n - R`; + - the lowest page is interpreted; + - nothing else is done. +5. **The documents.** The range tables go, and the rules take their place. `experiments/bare_metal/ + README.md` rule 3 ("file order") goes. +