Robert Allan JamesandClaude Sonnet 5
9886ad5315
Added 4055-4059 (former common/msg.4th) and 4300-4399 (former
process.4th) as reserved, each noted as freed by this reshuffle's
strip rather than owned by non-capsule infrastructure -- the file's
usual purpose (Artemis's own block usage, etc.). Framed explicitly as
lifted, not permanent, once someone deliberately wants a range back,
per FABRIC-3.5.md SSXVIII.4/XXII.4: freed ranges should be returned
here rather than silently available for a future capsule to reclaim
without anyone noticing.
mkcapsule --lint capsules/ clean, 37 files / 0 violations.
check_reserved_conflicts() -- the hard build-gate that actually reads
this file (tools/mkcapsule.c:974) -- passes clean on a real
`make -f Makefile.starkernel ARCH=amd64 all`, confirming the new
entries don't collide with anything currently baked. Registry/
documentation only, no capsule content touched, so no 3-arch boot run
for this task.
All of Phase 0's strips and documentation corrections (0.1-0.6) are
now done. stadium_conserved() (0.7) and the PLOT/FB-WIDTH/FB-HEIGHT
registration audit (0.8) remain.
Authorized by Captain Bob ("Go for it.").
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
38 lines
2.0 KiB
Plaintext
38 lines
2.0 KiB
Plaintext
# 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
|