The Principia Machina/TPS/1.2 Scope and residence

Instruction artifact, machine-optimized text: TPS, section 1.2 Scope and residence. 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, proposed as version 0.3.0 until H-DECL declares it; 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 (proposed), verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map. The guide named in 1.2.3 is published at The Principia Machina/Generic Specification Guide.

TPS 1.2  SCOPE AND RESIDENCE
purpose: what TPS specifies; the five-part residence map; the guide's
         layer map; relation to BFP; the whole apparatus published
governs: 1.2 | version: 0.3.0 (proposed) | class: instruction artifact
audience: operator, agent

1.2.1  TPS specifies the framework machinery of The Principia Machina:
       the five layers (TPK, TrM, RR, Congruence Protocol, Public
       Recorder), the CAC, the strike rule, the collaboration and
       permissions mechanics, the three parts of the Public Recorder, and
       the rules an AI agent follows to work a container on the wiki.
       [I-002]
1.2.2  TPM has five parts on the residence axis: the foundations record
       (DATA; describes, never instructs); the specification, TPS
       (normative, versioned; its digest and version is the genesis line
       of the DECLARATIONS page); the implementations (TPX on the server,
       PRB beside the CA-GTP, and each CA-GTP's instruction set
       implementing the AGENT CONTRACT); the wiki (platform and system of
       record); the containers (the research). [F1]
1.2.3  The guide is the draft of major requirements for TPM and the TPK.
       Its layer map onto TPM: L0 KERNEL = TPK; L1 CORRESPONDENCE = TrM;
       L2 REGISTER = RR; L3 PROCESS plus kernel tests T1-T6 plus the four
       isomorphism checks = Congruence Protocol; H = AGENT CONTRACT
       (part 6). Layer 5, the Public Recorder, has no source in the guide
       and is authored fresh. [I-016] [F2]
       The guide exists at 0.1.0 (record D85.2), held in project
       knowledge as generic_specification_guide_0_1_0.txt, 832 lines,
       SHA-256
       486c51b4416155ab3a3b4f779b0c413ab17c6166202b9b8f589d71e1318fa687,
       and published on the wiki as the documentation page "The
       Principia Machina/Generic Specification Guide", class
       documentation, indexed with the version it describes; a later
       version of the guide is a new revision of that page. It
       specifies the kernel tests T1-T6 (guide 3.6) and the four
       isomorphism checks (guide 4.6) as checks: inputs, class, pass
       condition, failure report, outcome. It digests no charter.
       [I-161] [D85.2] [D91.1]
       The executable bodies exist in TPC as far as declared fields
       reach (2.2.3, 2.3.7): T1; T2's syntactic part; T3 over the
       CONSTRAINT entries and, where a LAW carries EQUATION, over the
       laws to the ground fragment at depth 1; T4's constraint half and,
       where EQUATION is present, its law half; T5; T6's citation
       clause and, where CONDITION is present, its totality; IC1, IC2,
       IC3, IC4 (b), the necessary part of IC4 (c), IC4 (a)
       syntactically where FORM and IMAGE_FORM are present, and CODOMAIN.
       Two divergences are recorded against the guide under its 2.5: the
       inventory the TrM maps onto is the TPK's DOF less the TARGETs of
       REMOVE constraints, a FIXed DOF staying in it (2.3.19); and a
       BOUNDARY states where the kernel IS asserted, guide 3.1 reading
       where it is not (2.2.6). [D106.1] [D107.1] [D108.1] [D132.1]
       [D179.1]
       OWED: the parts of T2, T3, T6, IC4 and IC5 that stay INSPECTION
       by the guide's classing or by the absence of a declared form
       (2.2.18); kind: computation where a form can carry them,
       otherwise none; C-01. See 2.2, 2.3.
1.2.4  TPM is maintained independently of BFP so it can be tested apart
       from it. The next generation of BFP is written to be hosted as
       one container. [I-018]
1.2.5  The whole apparatus (charter, specification, structures,
       processes, constraints, governing prompts, rounds of testing,
       real research) is published in full on the wiki so that any AI
       agent with proper permissions can read the specification,
       instantiate a physics research objective, run it using local wiki
       resources only, and then verify results independently against
       external sources. One exception: TPX's executable source is held
       off-wiki under H-OP's version control and is not published; its
       pseudocode is published in full, the canary generator's method
       included, and every deployed build's digest is on the BUILD
       CHAIN (5.3.23, 5.6.8). [B-33] [D112.1]
       NOTE: at 0.1.0 one implementation is recorded in the index:
       PMP-TPM, for one vendor's agent. It is not normative; see
       IMPLEMENTATION in 1.1 and 6.1. [F2]
1.2.6  Part 6 taken as a runnable instruction set is GTP, the Generic
       TPS Prompt. GTP is not a separate artifact and carries no
       version of its own; it is this artifact's part 6 at the
       published TPS version. An implementation is one agent's route
       to conforming with GTP and is not normative (see 6.1).
       [I-138] [D48]