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:
@@ -1,37 +0,0 @@
|
||||
# capsule-reserved.txt — human-authored, git-tracked block ranges NOT
|
||||
# owned by any capsule (FABRIC-3.md §XXIV, 2026-09-12).
|
||||
#
|
||||
# mkcapsule can already catch a capsule colliding with ANOTHER capsule --
|
||||
# every capsule is a .4th file it scans. It has zero visibility into a
|
||||
# block something else owns: Artemis's own non-capsule persistent data
|
||||
# (identity records, home-blocks fence, etc.), or anything similar added
|
||||
# later. This file is how a human tells it.
|
||||
#
|
||||
# Format, one range per line:
|
||||
# START-END description
|
||||
#
|
||||
# START and END are inclusive logical block numbers (LBN). Lines starting
|
||||
# with '#' and blank lines are ignored. Checked by both the plain build
|
||||
# gate (check_reserved_conflicts(), hard-fails on collision) and
|
||||
# `mkcapsule --resolve` (suggests renumbering around these too).
|
||||
#
|
||||
# Known device boundaries, for reference when adding entries (not
|
||||
# reserved ranges themselves -- ramdrive is legitimately shared/reused by
|
||||
# capsules; only entries below reserve anything):
|
||||
# 2048-3071 volatile ramdrive (capsule_loader.c, KRD_MAX_BLOCKS=1024)
|
||||
# 3072+ Artemis's real virtio-blk device (persistent, disk/artemis.img)
|
||||
#
|
||||
# No ranges reserved yet for non-capsule infrastructure (Artemis's own
|
||||
# actual block usage becomes known from block_subsystem.c's BAM/
|
||||
# home-blocks fence accounting, not guessed) -- but see below for a
|
||||
# second, narrower use: recording a block range a capsule strip just
|
||||
# freed, so mkcapsule's collision machinery won't let a future capsule
|
||||
# silently reclaim it before a human decides to (FABRIC-3.5.md SXXII.4,
|
||||
# SXVIII.4). These are lifted, not permanent, once someone deliberately
|
||||
# wants the range back.
|
||||
|
||||
# Freed 2026-09-19 by the Tripod/kernel reshuffle's Category A surgical
|
||||
# strip (FABRIC-3.6.md tasks 0.2/0.3; see capsules/MANIFEST.md's
|
||||
# "Deleted capsules" section for the full account):
|
||||
4055-4059 formerly common/msg.4th -- deleted, block content confirmed dead by all three FABRIC-3.5.md SXXII.2 routes
|
||||
4300-4399 formerly process.4th -- deleted, block content confirmed dead by all three FABRIC-3.5.md SXXII.2 routes
|
||||
+30
-583
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user