5.5 The new-container flow (TPS 0.2.0)

Instruction artifact, machine-optimized text: TPS, section 5.5 The new-container flow. 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 changed only the status lines. This page is revision 5 of the tree, proposed as version 0.2.0 until H-DECL declares it. The text below is this section of the TPS artifact at 0.2.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 5.5  THE NEW-CONTAINER FLOW
purpose: initiators; zone order and per-zone checks; the final pass;
         the human declaration and initialization; the change-request
         redirect; the local-AI path
governs: 5.5 | version: 0.2.0 (proposed) | class: instruction artifact
audience: operator, agent

5.5.1  Initiators: any human account, or any account in the agent group.
       A human uses the new-container form; a CA-GTP writes its DRAFT
       UWC through TPX's API (see 1.1). [I-056] [I-041]
5.5.2  The three zones are entered in order, TPK, TrM, TMS. TPX runs each
       zone's checks as the zone is entered (the guide's kernel tests
       T1-T6; the four isomorphism checks; SR9 C1-C5) and returns a
       rejected component to the author. As the TPK is entered: T1,
       then T2's syntactic part and T5, then T4's law half, T6's
       totality and the names check where a LAW carries EQUATION or a
       BOUNDARY carries CONDITION; a T1 failure stops the run. A
       CONSTANT's UNIT is checked against its DIMENSION and the UNIT a
       FIX CONSTRAINT requires against its TARGET DOF's (2.2.9, 2.2.10).
       As the TrM is entered, header first: IC1, IC2, IC3, IC4 (b) and
       the necessary part of IC4 (c), IC4 (a) where a SIGNATURE carries
       FORM and IMAGE_FORM, and CODOMAIN (an entry on a REMOVEd DOF is
       refused); an untied DOF is held as a named gap (2.3.12-2.3.14,
       2.3.19). T3 reads STEP_CONVENTION and S_MAX from the TMS and
       runs at the final pass, after the TMS is entered, over the
       CONSTRAINT entries and over laws to the ground fragment, beside
       IC2's disposition under the TMS's IC2_POLICY (2.3.6); the TMS
       check (SR9), T3 and that disposition are the last gate. [I-057]
       [I-077] [D98.1] [D104.1] [D106.1] [D107.1] [D108.1] [D132.1]
       NOTE: where a check or a part of one is INSPECTION (2.2.18,
       2.3.14), it is INSPECTION by H-DECL before the declaration (see
       2.2.4, 2.3.8, 4.2 rows 34 and 35, 4.2.10). [DI-4.1]
5.5.3  On the final pass TPX computes D(TPK), D(TrM), D(TMS), D(TFK),
       obtains the UUID, allocates the prefix under D1's uniqueness
       check, and writes the candidate certificate to staging. Before
       the human declaration no UUID is in use and no register exists.
       [I-058]
5.5.4  H-DECL lands the certificate on the DECLARATIONS page: state
       CERTIFIED, with the ACCESS POLICY and the H-OWN binding, H-OWN
       being the initiator. On that landing TPX writes the TFK pages
       from the draft, digest-verified against the certificate, and
       initializes the register (volume 1 OPEN; master record = the
       certificate), the control panel, the lock, collaboration and
       access-list pages, the manifest, library page and badge, and the
       first BUILD CHAIN line. [I-059] [I-150] [I-152]
5.5.5  The draft is then protected read-only and indexed under the
       container as provenance (see 1.1, DRAFT UWC). [I-041]
5.5.6  CHANGE-REQUEST REDIRECT. An attempt to modify an established TFK
       is refused and redirected to this flow, pre-filled from the source
       when COPY-FORWARD is chosen and empty otherwise. The successor
       takes a new UUID and a new prefix and passes the same checks (see
       3.4). [I-060]
5.5.7  The Public Recorder digests no documents. A human holding a
       document hands it to a local AI; the AI enters the TFK through
       TPX's API if it is a CA-GTP, or the human enters the AI's output
       through the form. [I-054]
       The zone-by-zone check order is 5.5.2 and the per-component
       rejection form is 2.5.14 (D98.1, D99.1, D106.1-D108.1).
       OWED: the new-container page's presentation of both; kind:
       absence; C-12.
5.5.8  The TrM zone is entered header first, then the entries. TPX
       runs the 2.3 checks as the zone is entered and returns a
       rejected component to its author (see 2.3.10 to 2.3.16).
       [D39.1]
5.5.9  The new-container form carries the ACCESS POLICY selection, OPEN
       or CLOSED, and seeds the access list when CLOSED (see 5.16); it
       carries the AUDIT TRIGGER selection, AUTOMATIC or ON REQUEST,
       declared in UWC STATE with the policy, fleet default AUTOMATIC;
       COMMUNITY PARROTS starts at the fleet default ACCEPT and is
       H-OP's tuning option thereafter (5.16.11). On the final pass TPX
       also fixes the register's reserved range for its own writes
       (3.1.11). [I-150] [D52] [D111.1] [D119.1]
5.5.10 At the first DATABASE LEVEL a new UWC needs H-OP's confirmation before
       its instantiation (5.3.39). The register is initialized in VOLUME SIZE
       volumes (3.1.12), TPX's reserved range whole volumes (3.1.13). [D136.1]
       [D140.1]
5.5.11 THE BIBLIOGRAPHY AT THE FORM (D170.1). The new-container form
       carries the BIBLIOGRAPHY SETTING selection, OFF or ON, beside ACCESS
       POLICY and AUDIT TRIGGER, OFF unless the initiator selects ON; the
       DRAFT UWC API takes the same selection, default OFF. H-DECL declares
       it in UWC STATE with the certificate (5.5.4, 5.6.14); on that
       landing under ON, TPX initializes Bibliography Volume 1 with the
       register (5.21.1). [D170.1]