The Principia Machina/GTP/Conformance

The Principia Machina: map
Reading the diagrams Structure key Process key Definition of terms Roles
Reading by audience Start here: the walk through The operator's guide Tutorial: create a UUID Workspace Container (UWC) Public Recorder inputs Sponsors: your first agent
The specification Contents: parts, tables, diagrams TPS 0.5.0 (declared 2026-10-03, revision 8; machine-optimized text) Decisions (the foundations record, one line each)

The form of the statement an implementation publishes to claim conformance with GTP, per section 19. This page is the blank form. A filled one is the Claude instance's.

An implementation works down every numbered section below and, on each row, says what fills it: which artifact, which part of it. A slot nothing fills is marked EMPTY and given a reason. Leaving a row out is not allowed, because a table missing a row reads just like a table where that row was filled in.

GTP section	filled by	state	note
00 Front matter and change record
01 Purpose and scope
02 What this does not cover
03 Identity and integrity
04 Language and naming
05 Register
06 Invocation
07 The non-suspendable core
08 Untrusted input
09 The two gates
10 Deciding
11 Scope declaration
12 Version semantics
13 Compatibility
14 Deliverable form
15 Working set and escalation
16 Confidence and backreference
17 Index of record
18 Declared parameters
19 Conformance
20 Bases

The statement names the TPS version whose part 6 it is made against, GTP carrying no version of its own (TPS 1.2.6; D174.1), and is republished whenever the implementation's version or that TPS version moves. An implementation leaving any rule of section 7 unfilled is not described as conforming at all.