Jump to content

The Principia Machina/TPS/2.1 The Full Kernel and immutability: Difference between revisions

From The Invariance Itself
TPM>BFP_Rauch
TPS 0.2.0 (proposed) revision 5 rebuilt (v15): D91.1-D173.1 under tpm_tps_thread_request 0.1.9 and the bibliography resolution of 2026-09-26
m 1 revision imported
(No difference)

Revision as of 16:05, 26 September 2026

Instruction artifact, machine-optimized text: TPS, section 2.1 The Full Kernel and immutability. 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 changed only the status lines. This page is revision 5 of the tree, proposed as version 0.2.0 until H-DECL declares it. The text below is this section of the TPS artifact at 0.2.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 2.1  THE FULL KERNEL AND IMMUTABILITY
purpose: the three zones; immutable fields against mutable fields
         carried by register records; a change is a new container; the
         yardstick-only successor
governs: 2.1 | version: 0.2.0 (proposed) | class: instruction artifact
audience: operator, agent

2.1.1  Immutable, the three zones of the TFK: the TPK in full; the TrM
       header and, for each TrM entry, the identification fields only:
       NAME, DOF, DOMAIN, ENVIRONMENT_QUANTITY, the identification
       itself, FALSIFIER, FALSIFIER_CLASS, BEARS, DIMENSION; and the TMS
       in full (2.3.10, 2.3.11). [B-05] [I-023] [D39.1] [D98.1]
2.1.2  The TFK is immutable per container. Any change to it instantiates
       a new container with a new UUID and new prefix by COPY-FORWARD; a
       same-digest fork still enters PROVISIONAL (D5). [I-061]
2.1.3  Mutable, carried by register records that name the entry: STATE,
       SCRUTINY, RIDER, NOTE, CHECKS OWED, RECORDS. The entry form inside
       the TFK carries no status. [B-05]
2.1.4  A change to any immutable field moves D(TFK) and instantiates a
       new container per D5 (see 3.4). [B-05]
2.1.5  Containers sharing a TPK are recognizable by a shared D(TPK); a
       successor with D(TPK) and D(TrM) unchanged and D(TMS) moved is a
       yardstick-only successor, which the re-audit scope rule (see 4.1)
       may narrow on. [B-05]
2.1.6  IMMUTABLE is the adjective for the TFK and its fields; STATIC,
       FIXED and FROZEN are not used for this (see 1.1). [I-029]
2.1.7  The immutable TrM zone is the TrM header and the per-entry
       identification fields. A change to either is a change to the TFK
       (see 2.3). [D39.1]