Jump to content

The Principia Machina/TPS/5.5 The new-container flow: Difference between revisions

From The Invariance Itself
Post-TPC-PY page batch B2 (S90, S130): TPS revision 7 (proposed TPS 0.4.0)
m 1 revision imported
(No difference)

Revision as of 02:11, 30 September 2026

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, which changed only the status lines, was declared final on 2026-09-26, and TPS 0.3.0, revision 6, on 2026-09-28. This page is revision 7 of the tree, proposed as version 0.4.0 until H-DECL declares it; revision 6 is carried whole, and revision 5, proposed as 0.2.0, stays undeclared. The text below is this section of the TPS artifact at 0.4.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; the structure class; the switches
         and the check page; the closed world; ENVIRONMENT MODULES in
         the flow
governs: 5.5 | version: 0.4.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]
       AMENDED (D176.1, D177.1). As the TPK is entered T1 also reads
       the PARAMETERS part, every LAW's ROLE and every DOF's ROLE, and
       applies the D VARIABLE rules under D_VARIABLES (2.2.6, 2.2.13).
       The structure check runs at the final pass, after T3 and IC2's
       disposition, over the TFK whole, since it reads STRUCTURE_CHECK
       from the TMS; it belongs to the last gate and refuses nothing
       (2.2.20). [D176.1] [D177.1]
5.5.3  On the final pass TPX computes D(TPK), D(TrM), D(TMS), D(TFK)
       and the class (2.2.20), obtains the UUID, allocates the prefix
       under D1's uniqueness check, and writes the candidate
       certificate to staging, its STRUCTURE LINE carrying the class,
       its reasons and, under STRUCTURE_CHECK ON, the findings and
       lines listed for H-DECL, the UNDER gaps among them. H-DECL
       declares the class with the certificate; TPX shows it on the
       control panel, the manifest and the library page and never
       rewrites it. Before the human declaration no UUID is in use and
       no register exists. [I-058] [D176.1]
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; the MASTER at <prefix>-1
       (3.3.1), then one NAMED_GAP per IC2 and UNDER gap from
       <prefix>-2, sorted by SOURCE then DOF (3.3.5)), the control
       panel, the lock, collaboration and access-list pages, the
       manifest, library page and badge, and the first BUILD CHAIN line;
       for a successor by COPY-FORWARD it writes, before the badge, the
       entries (3.4.9), then the inherited records and their WITHDRAWALs
       of cause INHERITED (3.4.2). [I-059] [I-150] [I-152] [D192.2]
       [D199.1] [D215.2]
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). After an SR7 DOMAIN restriction H-DECL declares
       on a record carrying DOMAIN_CONDITION, the successor's pre-filled
       draft gains that condition as a BOUNDARY CONDITION for its author
       to keep or edit. [I-060] [D197.2]
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]
5.5.12 THE SWITCHES AND THE CHECK PAGE (D176.1, D177.1). The two
       switches are fields of the zones, written by the author in the
       draft and through the DRAFT UWC API alike, never selections of
       the form: STRUCTURE_CHECK in the TMS's PARAMETERS (2.4.7) and
       D_VARIABLES in the TPK's PARAMETERS part (2.2.6), each at its
       default when left out, which the form shows as "(default, not
       chosen)". Both lie inside D(TFK), are declared by H-DECL with
       the TFK and are fixed for the life of the UWC; COPY-FORWARD
       pre-fills both from the source (5.5.6). The draft's check page
       shows the EOM MAP, the findings and the class the final pass
       would give, under either value of STRUCTURE_CHECK: the switch
       governs the gate, not the preview. On the landing that
       instantiates a UWC whose STRUCTURE LINE names UNDER under
       STRUCTURE_CHECK ON, TPX opens EOM-0 (3.3.16). [D176.1] [D177.1]
5.5.13 THE CLOSED WORLD AT THE GATE (S1). The flow certifies a TFK that
       asserts exactly what its entries state and nothing else (2.2.19):
       an interaction the author leaves out is absent from the UWC, not
       assumed, and no check reports an interaction the entries omit
       (2.2.5). H-DECL reads each law in prose against this rule before
       the declaration (2.2.18, 5.5.2). [S1]
5.5.14 ENVIRONMENT MODULES IN THE FLOW (D178.1). Every draft carries the
       interview's answer (5.22.4); each chosen ENVIRONMENT MODULE is
       bound once the DOF and laws its slots name exist, TPX writing the
       expansion into the draft (5.22.7), and the zone checks of 5.5.2
       read the expanded TPK as any TPK. The final pass runs only on an
       answer that covers the OFFER in force (5.22.5); it re-expands
       MODULES USED (5.22.8) and computes each claim's status (5.22.14).
       The candidate certificate carries MODULES USED beside the
       digests, outside D(TFK), and the staging page shows the check
       page's summary to H-DECL whichever path made the draft (5.22.6).
       COPY-FORWARD's pre-fill carries the source's claims (3.4.10).
       [D178.1]