Capsule blocks step 2: mkcapsule makes no claims -- a later write overwrites
Captain Bob ruled "Overwrite. That's it. Deterministic and final", within a capsule and across capsules, "consistent with VOCABULARY FORGET & FENCE philosophy, not implementation". Of what only prevented collisions: "All of it goes". - The cross-capsule collision gate is gone. - tools/capsule-reserved.txt and its check are gone. - The interactive resolver and its claim registry are gone. - BLOCK_MAP.md says "Blocks used", and marks a shared number "the later write overwrites". It is a convenience, not a gate. - An unknown option is refused with the usage. A removed mode was otherwise taken for the capsules directory, with its next argument as the output file. Test first: scripts/test_mkcapsule_overwrite.sh, 9 checks. - The before-run failed 7. A repeat within one capsule already built, since there was never a check for it. - After: all 9 pass. step 1's test still passes, the amd64 build is clean, all 40 capsules lint, and the mesh boot passes 109 checks with POST 990/990. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
@@ -0,0 +1,9 @@
|
||||
FAIL: two capsules sharing a block number build
|
||||
PASS: one capsule repeating a block number builds
|
||||
FAIL: a page in a once-reserved range builds
|
||||
FAIL: and tools/capsule-reserved.txt is gone
|
||||
FAIL: --resolve is no longer a mode: it is answered with the usage
|
||||
FAIL: and the tool has no such mode
|
||||
FAIL: the map says Blocks used
|
||||
FAIL: and calls no number a conflict
|
||||
RESULT: FAIL
|
||||
Reference in New Issue
Block a user