Jump to content

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

From The Invariance Itself
m 1 revision imported
TPS 0.1.0 page 2.1 The Full Kernel and immutability, verbatim unit
(No difference)

Revision as of 19:59, 17 September 2026

Instruction artifact: TPS 0.1.0, page 2.1 The Full Kernel and immutability. Part of TPS 0.1.0 and the TPM hub. Human-only edit (TPS 5.13). Version 0.1.0, proposed; declaration pending. Governing section: this page, TPS 2.1. The text below is this page's unit of the TPS 0.1.0 artifact, verbatim; the whole artifact and its file digest are on The Principia Machina/TPS 0.1.0.

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.1.0 (proposed) | class: instruction artifact
audience: operator, agent

2.1.1  Immutable, the three zones of the TFK: the TPK in full; for each
       TrM entry the identification fields only: DOF, DOMAIN, the
       identification itself, FALSIFIER, BEARS; and the TMS in full.
       [B-05] [I-023]
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]