The Principia Machina/TPS/5.5 The new-container flow

Instruction artifact, machine-optimized text: TPS 0.1.1, section 5.5 The new-container flow. Part of TPS 0.1.1 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). Version 0.1.1 changes only the status lines (this lead, the title's version and the header's version line); H-DECL declares it. The text below is this section of the TPS 0.1.1 artifact, 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.1.1 | 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; an agent 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. The TMS check is the last gate.
       [I-057] [I-077]
       NOTE: while a kernel-test or isomorphism-check body is owed, that
       check is INSPECTION by H-DECL before the declaration (see 2.2.4,
       2.3.8, 4.2 rows 34 and 35). [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 certified agent, or the human enters the AI's
       output through the form. [I-054]
       OWED: the zone-by-zone check order for the new-container page and
       the per-component rejection form; 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).
       [I-150] [D52]