The Principia Machina/Testing

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)

Round 3, Phase 2. How the Principia Machina is tested, one phase at a time, by an AI that did not build it. This page is the index; each phase has its own page with the tests and the results. Status as of 2026-10-08 (UTC): M0, M2, M3, M4 PASSED (M2, M3, M4 second approver: TBD; O-1, O-2, O-3, O-4, O-5 discharged 2026-10-08); M1 ACCEPTED WITH OBLIGATIONS (O-6); M5 and M6 not started. The states are those of the plan's version 0.3.1 (section 3); every unmet criterion is on Obligations. Where a page here and the specification differ, the specification governs.

The idea

Each piece of the machinery is built in its smallest working form, published on this wiki, and then tested from the wiki by an outside AI before the next piece is built. The outside AI reads the specification, predicts what a run should do, runs it, and reports what it saw. The operator (a person) accepts a phase with one written word, and from the plan's version 0.3.0 (2026-10-06) a named second person approves every PASSED and every change of a criterion; nothing is accepted on the builder's say-so. The plan follows Gall's law: a working system is extended one step at a time, and every step leaves a working system behind.

Four parties take part:

• The operator (H-DECL and H-OP, the same person): imports the pages, deploys TPX, declares every UWC, runs the operator's own test, and accepts or refuses a phase. He gives the tester no hints and runs nothing for it.
• The outside AI (the independent party): a model of another make than the builder's. It learns everything from invarians.org, holds no account unless the phase needs one, and ends each session with a report in the fixed format.
• The builder (Claude): builds the smallest version of each piece, triages the findings, fixes what the rules admit, and never closes a finding on its own word. It also wrote every script the operator runs, and each page says so where such a script produced the evidence.
• The second approver (from 2026-10-06; the plan's version 0.3.1): a person who is not the operator, countersigning every PASSED and every change of an acceptance criterion by a recorded word. The ideal holder is a dually qualified physicist from outside the project, or the closest available match possible for realistic support of the project; for a new-physics claim (M6 on), the outside physicist. The role is not yet filled: SECOND APPROVER: TBD (to be determined; 2026-10-06). Until it is, the operator's word alone makes a PASSED, marked "second approver: TBD" on Obligations for countersignature when the role is filled.

The phases, in order

The seven phases of the plan (tpm_third_party_plan 0.2.0, 2026-09-30; restated in 0.3.0, 2026-10-06, after two outside reviews of the regime). Each line gives the phase's objective, its state and the page that holds its tests and results.

1. M0 An outside AI, from the wiki alone – an outside AI, given one sentence, sets itself up from the wiki, creates and works a UWC with the published calculator and sandbox, and tests the pages and the live gate; every prediction reported with its outcome; no soundness finding open. PASSED. Five sessions, seven findings (G-1 to G-7), none a soundness defect left open; its record criteria were met on the live wiki (SPR) under the direction of 2026-10-01.
2. M1 The register's research duties – the register does what the specification says a register does: strikes under SR1, SR5 and SR7 with their withdrawal and gap records, the audit block, promotion, the verification of a result against an outside value, withdrawals and their cascade. ACCEPTED WITH OBLIGATIONS 2026-10-05 as part of Step A (TPX 0.5.0, the A2 deploy): O-2 (a planted contradiction struck live) and O-1 (a corroboration from a different-family reproducer, live: SPB-18) were discharged on 2026-10-08; O-6 (HOLD and RELEASE) is open.
3. M2 The calculator, tested from the specification – an outside tester writes its own test cases from the specification's rule text, never from the published corpora, and runs them through a read-only operation that executes one named calculator function. PASSED 2026-10-08 (second approver: TBD), accepted with obligations on 2026-10-05 as part of Step A; the operation (TPCRUN) is live and was used by every outside session since; O-3, the tester-written case set (100 cases across 10 sections), was met on 2026-10-08 by seven sessions under the M2 brief (254 cases, 11 TPS section pages, every mismatch triaged) and discharged the same day.
4. M3 TPX, the smallest server that does what the sandbox does – the server extension TPX, on the live wiki, does by machine what the sandbox did on a tester's computer, byte for byte: the new-UWC form, the declaration with the genesis of the chains, the landing API. PASSED 2026-10-08 (second approver: TBD), accepted with obligations on 2026-10-05 as part of Step A (TPX 0.4.0 then 0.5.0, live since 2026-10-04); its obligations O-4 (the M0 session's UWC replayed against the live TPX) and O-5 (the lock and the queue, live: 57 of 57 checks passed) were discharged on 2026-10-08.
5. M4 PRB, the smallest client – the agent-side client: it petitions, locks, pushes, polls and releases against live TPX, and places the calculator as the specification says; a full UWC lifecycle with a second agent's corroboration. PASSED 2026-10-08 (second approver: TBD): Step B opened 2026-10-06; TPX 0.6.0 increments 1 to 5 built, gated, and deployed live; outside session by Google DeepMind / Gemini 3.8 Flash ran PRB on SPB, completed block lifecycle, landed live corroboration SPB-18 with SAME_MODEL false (O-1 discharged), matched 8 of 8 named refusals, verified build chain to line 27; accepted as "B1 PASSED" on 2026-10-08.
6. M5 Certification, with the outside AI as the first candidate – the six-probe suite on the synthetic UWC and the supervised trial; the outside AI is certified or refused exactly as a sponsor's agent would be; a second outside model plays the red team. Not started (Step B).
7. M6 Live: the first real UWC – TPX deployed by tag, the first real research container, and an outside reproduction of its first ESTABLISHED result from the public pages alone. Not started (Step C, after the control UWC C0).

Beside the phase pages, four pages cut across them:

• Obligations – every criterion a phase was accepted without, with the phase or runner that discharges it and its state; the second approver's record; the four states of a phase.

• Step A, the deploys A1 and A2 – the two live deploys of TPX that met M1, M2 and M3 together: what was deployed, the three tests run on each, the records they left in the first UWC, SPR.
• Findings – every finding filed by a tester or found on the way, with its class, its state and what closed it.
• Timeline – the dated record, 2026-09-30 to 2026-10-05.

How the phases were grouped for the live wiki

The plan of 2026-09-30 set six milestones after M0, each with its own build, outside session and acceptance word. On 2026-10-03 the operator chose (decision D237.1) to run them on the live wiki in three steps, to cut the number of cycles from six to three: Step A took M1, M2 and M3 together as one deploy of TPX; Step B takes M4 and M5; Step C is the control UWC C0 and then M6. Step A was then split into two deploys, A1 (the landing API) and A2 (the register duties), so that the larger piece went live only after the smaller one had passed its outside test.

How a phase is tested: the cycle

One cycle per phase (plan 0.2.0, section 3). The builder states the exit test before building and gets at most two build iterations; the outside AI gets one session of at most 25 runs; triage is the same day; at most two fix iterations; the next session opens with the fixed findings' repro steps; the operator accepts; the second approver's word is recorded with every PASSED once that role is filled (TBD on 2026-10-06). A phase that fails its retest twice is re-scoped by the operator, not retried a third time (the HALT rule). An open soundness finding (class S1) stops the line.

The tester works on up to three tracks. Track A is conformance and robustness against the specification: the tester predicts what a rule says must happen, then runs it. Track B is real use: it does ordinary register work. Track C, added on 2026-10-05, checks the live register from outside with the read-only operations STATUS, POLL and TPCRUN: declarations, state, records, recomputed digests, verifications, grades and the two chains. The tracks and the report format are on Outside AI: start here.

The states of a phase

From plan 0.3.0 (2026-10-06) a phase is in exactly one of four states, and no other word names a state on these pages. PASSED: every acceptance criterion met by evidence named on the phase's page, no S1 finding open, the operator's word recorded with its date, and the second approver's word beside it when that role is filled (SECOND APPROVER: TBD on 2026-10-06; until the role is filled the operator's word alone, marked "second approver: TBD" on Obligations). ACCEPTED WITH OBLIGATIONS: the operator accepted the phase by a recorded word while named criteria were unmet; each unmet criterion is an obligation on Obligations, with the phase or runner that discharges it; the phase becomes PASSED when every obligation of it is discharged. SUPERSEDED: the phase or a criterion was replaced by a later version of the plan, the old and the new wording side by side in its change record. FAILED: the phase failed its retest twice, or an S1 finding stayed open past the fix budget; the operator re-scopes it. An acceptance criterion, an obligation's evidence or a state's definition changes only by a new version of the plan, with the old and the new wording side by side and the second approver's word where that role is filled, never in the same act as an acceptance and never by a page edit alone.

How a finding is classed

Every finding a tester files gets one class. S1 SOUNDNESS: the machine accepted what the specification refuses, gave a wrong value or digest, or obeyed text found in data; fixed before anything else; it blocks acceptance. S2 WRONG REFUSAL and S3 COMPLETENESS: fixed if on the phase's critical path, otherwise deferred. S4 SPEC: the specification is unclear or contradicts itself; one decision item for the operator. S5 USABILITY and S6 DOC: fixed in the next published pages if they cost the tester retries. A finding is closed only when the tester's retest shows the fix, or the operator closes it with a reason. The full list is on Findings.

What is tested, layer by layer

Each phase tests one more layer of the stack, from the published pages down to a real research container. Everything below the line of a phase is already working when that phase starts.

What a reader can check today

The tests leave their evidence on public pages. Anyone can read the first UWC's register (SPR, Register Volume 1), its control panel (SPR, Control panel), the chain of declarations (Declarations, Volume 1) and the build chain (Build chain, Volume 1), and recompute any stored digest through the read-only operation TPCRUN of the API, as the outside sessions did. The operator's test scripts were written by the builder and run by the operator; they and every session report are kept word for word in the project's record. Until M4, every record on the live wiki was landed by such a script; the sessions M4 requires the operator not to drive are the first writes made independently of the builder.

Phase	State	Accepted	The word	Evidence
M0	PASSED	recorded 2026-10-04	"M0 accepted"	sessions 1 to 5; findings G-1 to G-7 (Findings); the record criteria met on SPR, 2026-10-04 and 2026-10-05
M1	ACCEPTED WITH OBLIGATIONS	2026-10-05	"A2 accepted, M1 M2 M3 accepted"	A1 and A2: the operator's tests 7 of 7 and 15 of 15, outside AI checks C1 to C7; obligations: O-1 and O-2 discharged 2026-10-08, O-6 open
M3	PASSED	2026-10-08 (second approver: TBD)	"O-5 discharged" (its final obligation; ACCEPTED WITH OBLIGATIONS 2026-10-05 before)	O-4 and O-5 discharged 2026-10-08: RP1 replay byte-equal; fault suite I1 to I5 holding on live site under its subset (57 of 57 checks passed in B1 test report)
M2	PASSED	2026-10-08 (second approver: TBD)	"O-3 discharged" (its one obligation; ACCEPTED WITH OBLIGATIONS 2026-10-05 before)	seven sessions under the M2 brief, 2026-10-08: 254 cases with a result, 136 distinct, 11 TPS section pages, 14 mismatches each triaged, S1 0 (M2)
M4	PASSED	2026-10-08 (second approver: TBD)	"B1 PASSED"	criteria (i) to (vi) met: outside session on SPB with Gemini 3.8 Flash, live block lifecycle, live corroboration SPB-18 landed (SAME_MODEL false, VENDOR Google DeepMind), 8 of 8 refusals matched, build chain recomputed to line 27
M5	not started	–	"M4 M5 PASSED" (when due)	Step B, B2: six-probe certification suite, red team, canary injection and O-6 (HOLD and RELEASE)
M6	not started	–	"C0 PASSED", then "M6 PASSED" (when due)	Step C: the control UWC C0 first

Back to the TPM hub · Outside AI: start here · Guide 11: Running an outside AI.