3.1 Records, prefixes and volumes (TPS 0.1.0)

Instruction artifact: TPS 0.1.0, page 3.1 Records, prefixes and volumes. Part of TPS 0.1.0 and the TPM hub. Human-only edit (TPS 5.13). Version 0.1.0, proposed; declaration pending. Governing section: this page, TPS 3.1. The text below is this page's unit of the TPS 0.1.0 artifact, verbatim; the whole artifact and its file digest are on The Principia Machina/TPS 0.1.0.

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
governs: 3.1 | version: 0.1.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]