0.1 Front matter and change record (TPS 0.1.0)

Instruction artifact: TPS 0.1.0, page 0.1 Front matter and change record. 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 0.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 0.1  FRONT MATTER AND CHANGE RECORD
purpose: name, version line, NORMATIVE status, source statement, the
         sentinel form, and TPS's own change record
governs: 0.1 | version: 0.1.0 (proposed) | class: instruction artifact
audience: operator, agent

0.1.1  This artifact is TPS, The Principia Machina Specification. It is
       NORMATIVE: it states every rule of the TPM framework machinery.
       [F1] [F2]
0.1.2  TPS is one artifact. It carries the five layers, the three Public
       Recorder parts, the container model and the AGENT CONTRACT
       (part 6). [F2]
0.1.3  The version line above is a proposal until H-DECL lands the
       genesis line of the DECLARATIONS page, which names the digest and
       version of the published TPS. See 5.6, 5.11. [C-22] [DI-1.1]
0.1.4  Version numbers follow Semantic Versioning 2.0.0 (MAJOR.MINOR.
       PATCH). Under major version zero, renames and the landing of owed
       bodies are MINOR. [C-22] [DI-1.1]
0.1.5  The digest of a published TPS is computed by TPX. A
       hand-transcribed digest is not a digest. See 2.5. [I-062]
0.1.6  TPS cites the foundations record (tpm_foundations_record) as the
       source of every reason. The record is DATA; it instructs nothing.
       See 8.1. [F1] [B-42]
0.1.7  Rule text is imperative. A rule states what is done or never
       done. A rule that TPS cannot yet state is an OWED line. The
       keywords MUST, MUST NOT, MAY and their kin carry the meanings of
       RFC 2119 and RFC 8174 (see 8.3, S22). [AUTHORED] [B-46]
0.1.8  Sentinel form of the published artifact:
         END OF ARTIFACT --- TPS <version>
       followed by one line stating that its absence means truncation.
       An artifact received without it was truncated and is not saved.
       [AUTHORED]
CHANGE RECORD
  0.1.0  2026-09-17  Initial drafting by branch tps_full_specification
                     from PMP-TPM 0.2.0 (rules) and
                     tpm_foundations_record 0.5.0 (reasons), under the
                     selections D37.1, D38.2, DI-1.1, DI-3.1, DI-4.1.
                     Proposed; declaration pending.