Jump to content

5.1 The three parts and the placement rule (TPS 0.1.1)

From The Invariance Itself
Revision as of 13:33, 26 September 2026 by BFP Rauch (talk | contribs) (1 revision imported)

Instruction artifact, machine-optimized text: TPS 0.1.1, section 5.1 The three parts and the placement rule. Part of TPS 0.1.1 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). Version 0.1.1 changes only the status lines (this lead, the title's version and the header's version line); H-DECL declares it. The text below is this section of the TPS 0.1.1 artifact, verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.

TPS 5.1  THE THREE PARTS AND THE PLACEMENT RULE
purpose: PLATFORM, TPX, PRB; every deterministic responsibility is
         TPX's; the platform limits carried by design
governs: 5.1 | version: 0.1.1 | class: instruction artifact
audience: operator, agent

5.1.1  The Public Recorder is layer 5. It has three parts: PLATFORM, TPX,
       PRB (see 1.1). [I-044] [I-045] [I-046] [I-047]
5.1.2  The Public Recorder presents the UI through MediaWiki and owns
       every UI process MediaWiki does not handle natively: invoking the
       CAC, returning a rejected component to its author, allowing a
       passing TFK to be initialized with a UUID. [I-049]
5.1.3  PLACEMENT RULE. Every deterministic responsibility MediaWiki can
       host is TPX's: every MECHANICAL row of the check-class matrix
       (see 4.2); every digest, TPX being the sole implementation; the
       UUID; instantiation; the fencing check at the landing API; expiry
       evaluation; the manifest and badge, rebuilt at every landing with
       the badge last; D(IS), computed and published; access-policy
       enforcement (5.16); canary generation, delivery and scoring at
       the declared rate (5.17); the certification suite's execution
       and scoring (5.14); the scorecard and its two channels (5.18).
       No external script holds any of these. [I-050] [I-141] [I-146]
       [I-153] [I-154]
5.1.4  Platform limits carried by design: PHP work lives inside a web
       request; MediaWiki has no daemons and no cross-page transaction,
       so instantiation and landing are sequences with the badge written
       last as the commit marker; an external binary runs only under the
       shell framework's limits (see 7.1). [I-055] [I-131]
5.1.5  TPC, The Principia Calculator, is the defined set of pure
       functions TPM computes with: the digests and their combination;
       d(r); the SR3 tests; SR5 ordering; SR6 n_ind; SR8's S; the
       C-test harness; and, when their bodies land, the isomorphism
       checks and T1-T6. Its vectors are the synthetic suite and the
       report-only corpus (see 4.6.5). [D43.1] [D47.1]
5.1.6  TPC has two residences. TPC-PHP, the residence of record, is
       part of TPX and holds TPX's pure functions. TPC-PY is published
       and advisory and is PRB's computation; it holds no
       responsibility. [D43.1]
5.1.7  The placement rule is unchanged: every act of record is TPX's
       (see 5.1.3). PRECEDENCE: the TPS text, then TPX for operations.
       TPC-PY decides nothing. [D43.1]
5.1.8  COVERAGE RULE. Every TPC function has vectors and exists in both
       residences. MECHANICAL at build (see 4.2, row 47). [D43.1]
5.1.9  A compiled build of TPC-PY is a local convenience: never
       distributed, never of record. The suite and the corpus run under
       both the compiled build and the interpreter. [D43.1]