Diagram 05 Copy-forward
| The Principia Machina: map |
|---|
| Reading the diagrams Structure key Process key Definition of terms Roles |
| Reading by audience Start here: the walk through The operator's guide Tutorial: create a UUID Workspace Container (UWC) Public Recorder inputs Sponsors: your first agent |
| The specification Contents: parts, tables, diagrams TPS 0.5.0 (declared 2026-10-03, revision 8; machine-optimized text) Decisions (the foundations record, one line each) |
Structural diagram 5 of 13. Part of the TPM hub.
- KIND: process
- LANGUAGE: Mermaid
- GENERATED FROM: static, TPS 3.4, 5.5.6
- STATUS: hand-authored at TPS 0.1.0; checked against TPS 0.3.0 on 2026-09-28: owed a redraw (not drawn: the bibliography entries carried first, 3.4.9; the pre-fill of STRUCTURE_CHECK, D_VARIABLES and the environment module claims, 3.4.10); checked against revision 7 on 2026-09-29, declared final as TPS 0.4.0 on 2026-09-30: also owed a redraw (the drawing's back-pointer is named in FINDING, where revision 7 has the field INHERITS, 3.4.3; not drawn: the batch re-promotion when D(TPK) and D(TrM) are unchanged, 3.4.6); its 3.4.2 step redrawn by hand on 2026-09-29 for D215.2 (every copy PROVISIONAL, a WITHDRAWAL of cause INHERITED per REFUTED or WITHDRAWN predecessor); checked against revision 8, proposed as TPS 0.5.0, on 2026-09-30: its back-pointer step drawn with INHERITS (3.4.3) and a step added for the batch re-promotion (3.4.6), by hand on 2026-09-30, in both copies of the source; the redraw owed for 3.4.9 and 3.4.10 stands; superseded by TPX at its first build
- SOURCE SHA-256:
348cfadf4b01ecd08097f483b6db7ff98e0f5093bf86b8ad650ee29edc8421f0
Rendered live from the source, which is the text equivalent and is shown under the drawing. The key to the shapes is in the panel.
%% 05 Copy-forward. process/Mermaid sequence. Generated from: static, TPS 3.4, 5.5.6. sequenceDiagram participant H as Human participant X as TPX participant P as Predecessor container participant S as Successor container H->>X: change request against the TFK, or digest-gate failure X->>H: redirect to the new-container flow, pre-filled from the source (5.5.6) H->>X: declared TFK for the successor X->>S: new UUID, new prefix (3.4.1) X->>P: read records X->>S: each record a fresh allocation, its field INHERITS naming the predecessor's full identifier (3.4.3) X->>S: every copy PROVISIONAL, then a WITHDRAWAL of cause INHERITED per REFUTED or WITHDRAWN predecessor (3.4.2) X->>S: same checks as any container, first CAC under the re-audit scope rule (4.1.9) X->>S: when D(TPK) and D(TrM) equal the source's, one PROMOTION record re-promotes each inherited result that was ESTABLISHED and still meets promotion's conditions (3.4.6) Note over P,S: back-pointers are provenance, not binding (3.4.5)
Text equivalent
COPY-FORWARD is offered on a change request against the Full Kernel (TFK) or a digest-gate failure (5.5.6). TPX, the controller, redirects to the new-container flow pre-filled from the source, the switches STRUCTURE_CHECK and D_VARIABLES and the source's environment module claims among what is pre-filled (3.4.10, 5.5.12); the human declares the successor's TFK; TPX allocates a new UUID (universally unique identifier) and prefix (3.4.1); where the source keeps a bibliography, its entries are carried first, in number order, with back-pointers (3.4.9); TPX then copies each record as a fresh allocation whose field INHERITS names the predecessor's full identifier, its BLOCK, AUTHOR, VETTED_IN, TPS and D_IS kept and its STATUS starting UNMARKED (3.4.3); each lands PROVISIONAL (NOT GRADED kept); then, for each record whose predecessor is REFUTED or WITHDRAWN, TPX writes in the successor a WITHDRAWAL of cause INHERITED setting that grade, a REFUTED one also marking the copy STATUS REFUTED, so REFUTED is kept REFUTED and WITHDRAWN kept WITHDRAWN (3.4.1, 3.4.2, 3.3.3); TPX runs the same checks, the successor's first congruence and completeness audit (CAC) under the re-audit scope rule, TPC reaudit_scope (4.1.9), and, when D(TPK) and D(TrM) equal the source's, re-promotes in one PROMOTION record every inherited result that was ESTABLISHED and still meets promotion's conditions (3.4.6). Back-pointers are provenance, not binding (3.4.5).