The Principia Machina/TPS/3.4 Inheritance under copy-forward

Instruction artifact, machine-optimized text: TPS, section 3.4 Inheritance under copy-forward. 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. This page is revision 6 of the tree, declared final as TPS 0.3.0 by H-DECL on 2026-09-28; revision 5, proposed as 0.2.0, stays undeclared and is carried whole. The text below is this section of the TPS artifact at 0.3.0, verbatim, its header line still reading "proposed" as the text stood when it was declared; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.

TPS 3.4  INHERITANCE UNDER COPY-FORWARD
purpose: inherited records as fresh allocations, PROVISIONAL, REFUTED
         kept; back-pointers; promotion by re-derivation; batch
         re-promotion open; ENVIRONMENT MODULE claims carried
governs: 3.4 | version: 0.3.0 (proposed) | class: instruction artifact
audience: operator, agent

3.4.1  COPY-FORWARD is a standing Public Recorder operation: source
       container to new container, new UUID, new prefix, inherited
       records PROVISIONAL with REFUTED kept REFUTED, back-pointers per
       record (D5). Offered on a change request against the TFK or on a
       digest-gate failure (see 5.5, 2.5). [I-040]
3.4.2  Inherited records enter as PROVISIONAL regardless of predecessor
       tag, except REFUTED, which stays REFUTED. Promotion requires
       re-derivation under the new TPK. The predecessor tag is recorded
       in the back-pointer only. [B-04]
3.4.3  Each inherited record is a fresh allocation in the successor's
       prefix; its FINDING names the predecessor's full identifier.
       [B-04]
3.4.4  A same-digest fork still enters PROVISIONAL (see 2.1.2). [I-061]
3.4.5  Everything in the successor belongs to the new UUID; back-pointers
       are provenance, not binding. [I-060]
3.4.6  A retired predecessor's pages stay readable and its back-pointers
       resolve directly (see 5.11). [B-10]
       OWED: whether CAC may batch re-promote same-digest inherited
       records; kind: convention; C-05.
3.4.7  The re-audit scope rule for a successor's first CAC may narrow on
       a yardstick-only successor (see 2.1.5, 4.1). [C-06]
3.4.8  ASSUMPTION RECORDS inherit as records do (see 3.4.2, 3.4.3);
       an inherited record's ASSUMPTIONS field cites the successor's
       identifiers for them. [D41.2]
3.4.9  ENTRIES UNDER COPY-FORWARD (D170.1 (e)). A successor of a UWC whose
       BIBLIOGRAPHY SETTING is ON or CLOSED is ON and inherits the
       bibliography first: each entry, in number order, is a fresh BIB ID
       in the successor's prefix with a back-pointer and its CHECK LINE and
       NOTICES LINE as they stand, not looked up again at the copy; every
       inherited record's LITERATURE is then remapped through the
       back-pointers (5.21.2). A successor of an OFF UWC takes the form's
       choice. [D170.1]
3.4.10 ENVIRONMENT MODULES UNDER COPY-FORWARD (D178.1 (g)). A
       successor's pre-filled draft keeps the source certificate's
       MODULES USED as CARRIED claims, whatever their versions' status
       now, each status shown and none updated by the machine; its
       author keeps or re-selects each, a new claim naming an OFFERED
       version (5.22.5, 5.22.14). The successor's certification fixes
       its claims anew (5.22.15). [D178.1]