Jump to content

The Principia Machina/Diagrams/05 Copy-forward

From The Invariance Itself
Revision as of 20:38, 17 September 2026 by BFP Rauch (talk | contribs) (Diagram layer page 05 Copy-forward, TPS 0.1.0)

Structural diagram 5 of 12. Part of the TPM hub.

Rendered live from the source, which is the text equivalent and is shown under the drawing; a wide drawing scrolls sideways inside its frame.

Source (the text equivalent; Mermaid) 
%% 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; FINDING names the predecessor's full identifier (3.4.3)
  X->>S: tag PROVISIONAL; REFUTED stays REFUTED; predecessor tag in the back-pointer only (3.4.2)
  X->>S: same checks as any container; first CAC under the re-audit scope rule (4.1.9)
  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 TFK or a digest-gate failure (5.5.6). TPX redirects to the new-container flow pre-filled from the source; the human declares the successor's TFK; TPX allocates a new UUID and prefix (3.4.1), copies each record as a fresh allocation whose FINDING names the predecessor's full identifier (3.4.3), tags them PROVISIONAL with REFUTED kept and the predecessor tag in the back-pointer only (3.4.2), and runs the same checks with the successor's first CAC under the re-audit scope rule (4.1.9). Back-pointers are provenance, not binding (3.4.5).

Retrieved from "https://invarians.org/index.php?title=The_Principia_Machina/Diagrams/05_Copy-forward&oldid=1555"