# 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 -- seed this file as Artemis's own actual block
# usage becomes known (e.g. from block_subsystem.c's BAM/home-blocks
# fence accounting), rather than guessing.