plan capsule blocks: no chaining, developer responsible; the work, for ruling

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:26:22 +00:00
parent d36b78cc73
commit cda8aad8b2
+26 -1
View File
@@ -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 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 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 (`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.