1.3 System of record and containers (TPS 0.3.0)

Instruction artifact, machine-optimized text: TPS, section 1.3 System of record and containers. 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 1.3  SYSTEM OF RECORD AND CONTAINERS
purpose: the wiki as system of record and version control; where
         current state lives; the container as the sealed unit
governs: 1.3 | version: 0.3.0 (proposed) | class: instruction artifact
audience: operator, agent

1.3.1  The MediaWiki site is the system of record and the version control
       for every aspect of TPM and TPM-based research. Edit rights are
       limited, not open (see 5.13). The wiki holds authoritative
       history. TPX owns the mutex; a holder's grant authorizes it to
       request register writes of TPX, not to perform one. The current
       state of a collaborative container lives with the mutex holder
       for up to 24 hours, and a wiki copy's state is read from the
       badge (see 5.10). [I-014] [I-137] [D48]
1.3.2  A container is isolated with its TFK and its full register.
       Cross-container reduction is out of scope by design (see 7.1).
       [I-015]
1.3.3  A UWC is sealed with its TFK and its full register. The seal
       binds RESEARCH: no claim, citation or derivation crosses a UWC
       boundary. TPX's system-wide administrative read over register
       volumes, used for canary generation (5.17) and the scorecard
       (5.18), is not a research access and does not breach the seal.
       No cross-UWC content reaches a CA-GTP except as a PACKAGE (5.17.4).
       A cross-UWC parrot is a REPRODUCTION block in the source UWC,
       worked by an agent-group account that also works elsewhere; its
       result lands where that UWC's corroborations land, the community
       ledger for a cross-UWC pass (5.9.13). That is a seal exception by
       construction: the seal binds content, not accounts, and the
       residual, a CA-GTP's later work contaminated by another UWC's
       laws, is bounded to the block by 5.9.3. [I-142] [D50] [D118.1]
       [D119.1]