plan capsule blocks: (- is a build marker per block, loads verbatim; CI's hook an open stub for the SDK (Captain Bob)
Build / Image PC (push) Successful in 6m11s
Build / Image MILKV (push) Successful in 6m10s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 14m21s
Acceptance / Acceptance (pull_request) Failing after 8m10s
Build / Image RASPI (push) Successful in 6m1s

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 19:57:49 +00:00
parent dd3469f9a3
commit bcfca9fa19
+19 -16
View File
@@ -132,21 +132,24 @@ Each step is test first, then POST and the protocol:
- **v4:** the same nesting comment, in `capsules/v4/physics.4th` block 8204.
- **POST:** v3's 4 cases for it pass in v4.
**Ruled:**
1. **The magic number lives in both places.** `mkcapsule` recognises `(-` at build time, and
interpreting it also leaves the magic number at run time, for the loader to check.
2. **`(-` nests, as now.** Only the magic number is added; the 4 POST cases are unchanged.
3. **It is per named blob** ("Named blobs are well defined in the documents": MACHINE.md §1–2, the
trailer's source, typed by name). Read here as: a blob that opens with `(-` is a system blob, as a
magic number opens a file. Captain Bob to correct this if it is wrong.
4. **Where a system blob goes is open.** "I'm thinking either 3 or 1":
- (1) a new, read-only kernel ROM image holding the system blobs only;
- (3) the kernel's capsule directory holding the system blobs only, with every other blob loaded
from elsewhere (Artemis, the stick).
**As Captain Bob put it next, which supersedes the readings below** ("(- is more of a build
marker"):
- **It is per block.** "this particular block number": a block that opens with `(-` is marked.
- **At run time it loads verbatim,** like any block, "because it might be part of ongoing development
or a required dependency". `(-` is only the nesting comment there; there is no run-time magic
number.
- **At build it is a request to CI:** "asking the CI to consider this particular block number be
cleared for inclusion in the next iso image that qemu runs with".
- **What CI does with the request** (ruled): "Open ended stubs to be hooked into after we begin the
SDK later." So the stub is the record of the request, with nothing to act on it until the SDK.
Not (2), v4's node ROM.
**Kept:** `(-` nests, as now. v3's 4 POST cases are unchanged.
**Still to settle before any of it is built:**
- the choice between (1) and (3);
- what the run-time magic number is (a variable's value, or a cell the loader reads);
- what the loader does with an unmarked blob in each case.
**Superseded** (kept as the record of how it was first understood):
- the magic number "both" at build and at run;
- the reading "per named blob";
- the targets (1) a new kernel ROM image and (3) the capsule directory of system blobs only.
The "kernel ROM image" is now "the next iso image that qemu runs with".
**Nothing is built.** When the SDK begins, the hook is to be designed against these lines.