3.1 Records, prefixes and volumes (TPS 0.3.0)
Instruction artifact, machine-optimized text: TPS, section 3.1 Records, prefixes and volumes. Part of TPS and the TPM hub. Human-only edit (TPS 5.13). TPS 0.1.0 was declared final at revision 4 on 2026-09-22, a version declaration recorded in the foundations record; the chain begins at TPX's first landing (TPS 5.6.7). TPS 0.1.1, which changed only the status lines, was declared final on 2026-09-26. This page is revision 6 of the tree, proposed as version 0.3.0 until H-DECL declares it; revision 5, proposed as 0.2.0, stays undeclared and is carried whole. The text below is this section of the TPS artifact at 0.3.0 (proposed), verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.
TPS 3.1 RECORDS, PREFIXES AND VOLUMES
purpose: <prefix>-n; the prefix unique across TPM and its registry; the
high-water mark; cross-container citation; volumes OPEN and
FROZEN; TPX's reserved range; the bibliography beside the
register
governs: 3.1 | version: 0.3.0 (proposed) | class: instruction artifact
audience: operator, agent
3.1.1 A register record is <prefix>-n. The prefix is declared per
container and unique across TPM (D1). Bare RR names the layer
only. [I-024] [I-025]
3.1.2 Each container's manifest declares one record prefix, unique
across TPM, checked at CAC. [B-01]
3.1.3 BFP-next's first container declares RR, so RR-1..RR-855 import
unchanged. [B-01] [I-025]
3.1.4 The container of records is VOLUME: a fixed-size container of
records inside the register (guide L2). States OPEN and FROZEN
are inherited vocabulary and are kept. [I-026] [B-01]
3.1.5 One high-water mark per container. [B-01]
3.1.6 A cross-container citation carries the prefix by construction.
[B-01]
3.1.7 Every successor container under D5 declares a new prefix; the CAC
prefix registry is the allocation authority for prefixes (see
3.4). [B-01]
OWED: the prefix registry, the CAC's record of every prefix in
use, checked at certification; kind: computation; C-08.
3.1.8 The mutex holder is the sole allocation authority for the
container's identifier mark. Coworkers return results without
identifiers; the lead allocates on incorporation or leases a
reserved range and reclaims the unused part on return (see 5.7,
5.8). [I-081]
3.1.9 The register is initialized at instantiation with volume 1 OPEN
and the master record equal to the certificate. No register
exists before the certificate lands (see 5.5). [I-059] [I-058]
3.1.10 An OPEN volume is written by AI-LEAD only, protected by H-OP,
enforced by group right and TPX check. A FROZEN volume is
read-only for every account (see 5.13). [I-098] [I-099]
3.1.11 TPX's OWN WRITES. The records TPX writes on its own authority -
HOLD and RELEASE (3.3.11, 3.3.12) and a corroboration it writes
on a community-ledger MATCH (3.3.15) - are allocated from a
reserved range per register, fixed at instantiation, disjoint
from every coworker lease by construction, the leased-range form
of 5.7.5 with TPX as the lessee. The allocation is a TPC function
(tpx_allocate; 5.1.5). This is the one allocation the mutex
holder does not request (3.1.8). [D111.1] [D119.1]
3.1.12 VOLUMES (D140.1). Every register is kept in VOLUME pages of VOLUME SIZE
records (7.2.21), the same size for every UWC and for the life of the
UWC, never varied with the register or the TFK: record n lives on
volume ceil(n / VOLUME SIZE), titled "<UWC root>/Register/Volume <v>",
and a record's address is that page and the anchor of its identifier,
so a record's page follows from its number alone, for any reader and
any tool. [D140.1]
3.1.13 LEASES OF WHOLE VOLUMES; VOID (D140.1). A lease, TPX's reserved range
included (3.1.11, 5.7.5), is a whole number of volumes from a volume
boundary, at most 1,000 identifiers. The identifiers the mark skips to
reach a lease's boundary are written as one VOID line in their volume.
When a lease closes (its RETURN landed, or its block expired), every
identifier of it that holds no record is VOID: in each volume the lease
used, TPX writes one VOID line naming them; a whole volume it never
used is never created, its identifiers retired, as the RETURN's USED
RANGE shows. A VOID line is no record: it cites nothing and no TPC
function counts it. [D140.1]
3.1.14 FROZEN (D140.1). A register volume is FROZEN when each of its
identifiers is a record or VOID. FROZEN means that no record is added
and no record's assertion changes; TPX alone writes a record's status
into its text (3.2.13), a FROZEN volume included. The guide's "never
written again" (L2) is read that way; the guide's text is unchanged.
[D140.1]
3.1.15 SEARCH, COMPRESSION AND READING (D140.1, D141.1). A register page gives
the search index a summary (identifier, record class, DOMAIN and
FINDING), never its full text, digests or derivation steps; revisions
are compressed from before the first register page (5.2.6); a reading
view over any range of records is a TPX special page computed on demand
and stored nowhere (5.3.42). Storage is reclaimed only by compression,
never by deletion. [D140.1] [D141.1]
3.1.16 THE BIBLIOGRAPHY BESIDE THE REGISTER (D170.1, D171.1). A UWC whose
BIBLIOGRAPHY SETTING is ON or CLOSED (5.21.1) keeps a BIBLIOGRAPHY
beside its register and not in it (5.21.3): BIBLIOGRAPHY ENTRIES
"<prefix>-BIB<n>" under the same prefix, numbered on the BIBLIO
MARK, a second counter beside the high-water mark of 3.1.5, from
which TPX allocates at landing in push order, with no lease and no
VOID (5.21.4); kept in BIBLIOGRAPHY VOLUMES of BIBLIO VOLUME SIZE
entries, FROZEN when full, their status lines writable (5.21.8,
5.21.22). No entry is a register record and none is counted by any
rule of part 4. [D170.1] [D171.1] [D173.1]