The Principia Machina/Testing/M4 PRB, the smallest client - Revision history

DeltaS Zero: B1 PASSED: M4 passed on 2026-10-08 (second approver: TBD)

2026-10-09T06:51:12Z

B1 PASSED: M4 passed on 2026-10-08 (second approver: TBD)

← Older revision		Revision as of 06:51, 9 October 2026
Line 1:		Line 1:
	{{TPM map}}		{{TPM map}}
	{{DISPLAYTITLE:Testing M4: PRB, the smallest client}}		{{DISPLAYTITLE:Testing M4: PRB, the smallest client}}
	''Phase M4 of [[The Principia Machina/Testing\|Testing the Principia Machina]]. State: ~~UNDER WAY~~. Grouped with M5 as Step B by decision D237.1 (2026-10-03); Step B opened on 2026-10-06 (tpm_stepB_split 0.1.0: B1 = M4, B2 = M5). The items moved out of Step A – CORROBORATION landing, the reserved identifier range, the lock – are built here as TPX 0.6.0; HOLD and RELEASE go to M5. Accepted as "B1 PASSED" ~~under the~~ criteria ~~below~~ (plan 0.3.0).''		''Phase M4 of [[The Principia Machina/Testing\|Testing the Principia Machina]]. State: PASSED 2026-10-08 (second approver: TBD). Grouped with M5 as Step B by decision D237.1 (2026-10-03); Step B opened on 2026-10-06 (tpm_stepB_split 0.1.0: B1 = M4, B2 = M5). The items moved out of Step A – CORROBORATION landing, the reserved identifier range, the lock – are built here as TPX 0.6.0; HOLD and RELEASE go to M5. Accepted as "B1 PASSED" on 2026-10-08 (criteria (i) to (vi) met; O-1 and O-5 discharged; plan 0.3.1).''

	== Objective ==		== Objective ==

DeltaS Zero: status batch 0.1.4 (tpm_closeout_m1etc 0.1.0): the order of D255.1 met before TPX 0.6.0

2026-10-08T11:32:50Z

status batch 0.1.4 (tpm_closeout_m1etc 0.1.0): the order of D255.1 met before TPX 0.6.0

← Older revision		Revision as of 11:32, 8 October 2026
Line 110:		Line 110:
	* The operator's own run of the B1 test script (tpx_b1_test.py, written by the builder) on the live site: the block, the live subset of the fault suite (criterion (iii), O-5), the build line read back (criterion (v)).		* The operator's own run of the B1 test script (tpx_b1_test.py, written by the builder) on the live site: the block, the live subset of the fault suite (criterion (iii), O-5), the build line read back (criterion (v)).
	* The builder's recheck of the landed blocks from outside, read-only.		* The builder's recheck of the landed blocks from outside, read-only.
	* Before any of it: the A3 closeout, which ~~discharges~~ O-2 and O-4, ~~and~~ the status batch and one M2 session (the order of the user's selection D255.1).		* Before any of it: the A3 closeout, which discharged O-2 and O-4 (run 2026-10-07, discharged 2026-10-08), the status batch (imported 2026-10-07) and one M2 session (seven ran on 2026-10-08, each triaged): the order of the user's selection D255.1, met; no S1 is open.

	The fault suite (B1 increment 5) tests five invariants: I1 one holder at a time and a grant never issued twice; I2 no duplicate landing, a non-holder's push lands nothing; I3 a lost answer never changes a committed record's identity or digest; I4 a stale grant lands, releases and extends nothing; I5 a refused request writes nothing. Its scenarios FS-1 to FS-12 cover a duplicate PUSH after a lost answer, a repeated RELEASE, concurrent petition and poll, a delayed PUSH after release and re-grant, a replayed challenge answer, a session cookie invalidated mid-block, HEARTBEAT past the NO-PROGRESS LIMIT, the holder's crash, malformed server answers to PRB, a PUSH carrying a TPX-written field, a VERIFICATION before its TARGET, and citing a REFUTED or HELD record. PRB's LOST-ANSWER RULE: before any re-send it reads STATUS and the chain's last line.		The fault suite (B1 increment 5) tests five invariants: I1 one holder at a time and a grant never issued twice; I2 no duplicate landing, a non-holder's push lands nothing; I3 a lost answer never changes a committed record's identity or digest; I4 a stale grant lands, releases and extends nothing; I5 a refused request writes nothing. Its scenarios FS-1 to FS-12 cover a duplicate PUSH after a lost answer, a repeated RELEASE, concurrent petition and poll, a delayed PUSH after release and re-grant, a replayed challenge answer, a session cookie invalidated mid-block, HEARTBEAT past the NO-PROGRESS LIMIT, the holder's crash, malformed server answers to PRB, a PUSH carrying a TPX-written field, a VERIFICATION before its TARGET, and citing a REFUTED or HELD record. PRB's LOST-ANSWER RULE: before any re-send it reads STATUS and the chain's last line.
Line 129:		Line 129:

	[[Category:The Principia Machina]]		[[Category:The Principia Machina]]

BFP Rauch: 1 revision imported

2026-10-07T13:23:21Z

1 revision imported

← Older revision	Revision as of 13:23, 7 October 2026
(No difference)

DeltaS Zero: M4: UNDER WAY (Step B opened 2026-10-06); criteria (i) to (vi) of plan 0.3.0; the fault suite; IF-B-1 corrected: TPX 0.5.0 has no lock acquisition and no challenge; the second approver TBD (tpm_status 0.1.3)

2026-10-07T13:22:32Z

M4: UNDER WAY (Step B opened 2026-10-06); criteria (i) to (vi) of plan 0.3.0; the fault suite; IF-B-1 corrected: TPX 0.5.0 has no lock acquisition and no challenge; the second approver TBD (tpm_status 0.1.3)

← Older revision		Revision as of 13:22, 7 October 2026
Line 1:		Line 1:
	{{TPM map}}		{{TPM map}}
	{{DISPLAYTITLE:Testing M4: PRB, the smallest client}}		{{DISPLAYTITLE:Testing M4: PRB, the smallest client}}
	''Phase M4 of [[The Principia Machina/Testing\|Testing the Principia Machina]]. State: ~~NOT STARTED~~. Grouped with M5 as Step B by decision D237.1 (2026-10-03); ~~it opens once Step A's findings are closed and the~~ Step B ~~brief is written~~. The items moved out of Step A – CORROBORATION landing~~, HOLD and RELEASE~~, the reserved identifier range – ~~land~~ here.''		''Phase M4 of [[The Principia Machina/Testing\|Testing the Principia Machina]]. State: UNDER WAY. Grouped with M5 as Step B by decision D237.1 (2026-10-03); Step B opened on 2026-10-06 (tpm_stepB_split 0.1.0: B1 = M4, B2 = M5). The items moved out of Step A – CORROBORATION landing, the reserved identifier range, the lock – are built here as TPX 0.6.0; HOLD and RELEASE go to M5. Accepted as "B1 PASSED" under the criteria below (plan 0.3.0).''

	== Objective ==		== Objective ==
Line 7:		Line 7:
	The plan (tpm_third_party_plan 0.2.0, section 4) states M4 as ''PRB, the smallest client that drives TPX through its API''. PRB is the agent-side program described in [[The Principia Machina/TPS/5.4 PRB\|the specification]]: it signs in with the agent's bot password, petitions for a lock, polls, pushes records, returns a coworker's work, releases the lock, and carries the published calculator (TPC-PY) so that every value an agent presents was computed, never reasoned. M4 builds the least PRB that completes one block on the live wiki and tests it against the TPX that Step A left running.		The plan (tpm_third_party_plan 0.2.0, section 4) states M4 as ''PRB, the smallest client that drives TPX through its API''. PRB is the agent-side program described in [[The Principia Machina/TPS/5.4 PRB\|the specification]]: it signs in with the agent's bot password, petitions for a lock, polls, pushes records, returns a coworker's work, releases the lock, and carries the published calculator (TPC-PY) so that every value an agent presents was computed, never reasoned. M4 builds the least PRB that completes one block on the live wiki and tests it against the TPX that Step A left running.

	The plan's acceptance: one full block – petition, lock, push, release – completed from a session the operator did not drive, every presented digest recomputed equal by TPX at landing, ~~and~~ the execution challenge answered from executed code.		The plan's acceptance (version 0.3.0, "B1 PASSED"): (i) one full block – petition, lock, push, release – completed on a sandbox UWC from a session the operator did not drive, every presented digest recomputed equal by TPX at landing, the execution challenge answered from executed code; (ii) the first live CORROBORATION, written by TPX from a REPRODUCTION block worked by a second account of another make (discharges O-1); (iii) the five invariants of the fault suite holding on the live site under its subset (discharges O-5); (iv) an outside session predicting, then attempting, at least eight named refusals of the B1 brief, each refused as predicted; (v) the build line of the deployed 0.6.0 on the chain, equal to the digest the deploy script read back; (vi) no S1 finding open; and the obligations O-2 and O-4 of Step A discharged first. The operator reads each criterion's evidence; the second approver countersigns when that role is filled (SECOND APPROVER: TBD on 2026-10-06; plan 0.3.1).

	<graphviz>		<graphviz>
Line 15:		Line 15:
	H [label="the human\n(sponsor; runs PRB)"];		H [label="the human\n(sponsor; runs PRB)"];
	M [label="the model's session\n(a CA-GTP, later;\nin M4 any session)", fillcolor="#ffedad"];		M [label="the model's session\n(a CA-GTP, later;\nin M4 any session)", fillcolor="#ffedad"];
	PRB [label="PRB\nthe client\~~nnot yet~~ built", shape=box3d, fillcolor="#ffedad", style="filled,dashed"];		PRB [label="PRB 0.1.0\nthe client\n(B1, being built)", shape=box3d, fillcolor="#ffedad", style="filled,dashed"];
	PY [label="TPC-PY 0.3.0\nplaced by PRB\nexecuted, never reasoned"];		PY [label="TPC-PY 0.3.0\nplaced by PRB\nexecuted, never reasoned"];
	API [label="api.php\naction=tpx"];		API [label="api.php\naction=tpx"];
	TPX [label="TPX 0.5.0~~\nlive~~ since 2026-10-05", shape=box3d, fillcolor="#cedff2"];		TPX [label="TPX 0.5.0 live since 2026-10-05;\n0.6.0 (B1) being built:\nthe lock, the challenge,\nthe reserved range, corroboration", shape=box3d, fillcolor="#cedff2"];
	W [label="the wiki\nSPR register, chains"];		W [label="the wiki\nSPR register, chains"];
	H -> PRB [label="starts"]; M -> PRB [label="records, requests"]; PRB -> PY [label="computes with"]; PRB -> API [label="PETITION, POLL,\nPUSH, RETURN, RELEASE"]; API -> TPX -> W;		H -> PRB [label="starts"]; M -> PRB [label="records, requests"]; PRB -> PY [label="computes with"]; PRB -> API [label="PETITION, POLL,\nPUSH, RETURN, RELEASE"]; API -> TPX -> W;
Line 27:		Line 27:

	{\| class="wikitable"		{\| class="wikitable"
	! Piece !! What the specification asks !! Where it stands on 2026-10-05		! Piece !! What the specification asks !! Where it stands on 2026-10-06
	\|-		\|-
	\| Sign-in \|\| A bot password made by the sponsor at Special:BotPasswords, with the grants the client needs (D228.1) \|\| The grants are listed in the PRB client specification (C-20); no PRB exists		\| Sign-in \|\| A bot password made by the sponsor at Special:BotPasswords, with the grants the client needs (D228.1) \|\| The grants are listed in the PRB client specification (C-20); no PRB exists
	\|-		\|-
	\| The block \|\| PETITION, then POLL until the lock is granted, PUSH, RELEASE; HEARTBEAT within the NO-PROGRESS LIMIT \|\| TPX~~'s side exists~~ and ~~was driven by~~ the ~~operator's scripts in A1~~ and A2		\| The block \|\| PETITION, then POLL until the lock is granted, PUSH, RELEASE; HEARTBEAT within the NO-PROGRESS LIMIT \|\| TPX 0.5.0 queues a petition and lands an unlocked push: no op acquires the lock, HEARTBEAT is uncapped (found at the Step B baseline read, 2026-10-06). The lock lifecycle – petition, acquisition at POLL, heartbeat under the NO-PROGRESS rule and the 24 h ceiling, release after a push, strict fencing – is built as B1 increment 1, gated 2026-10-06 (69 of 69; parity with the calculator 45 of 45), live with 0.6.0
	\|-		\|-
	\| The challenge \|\| At petition and on every push TPX issues a 128-bit nonce; PRB answers digest_fields(["TPC-EXECUTION-CHALLENGE", "1", nonce]) from executed code \|\| TPX~~'s side exists;~~ the ~~operator's scripts answer it from~~ the ~~published calculator~~		\| The challenge \|\| At petition and on every push TPX issues a 128-bit nonce; PRB answers digest_fields(["TPC-EXECUTION-CHALLENGE", "1", nonce]) from executed code \|\| Not in TPX 0.5.0 (the earlier text of this page was wrong: IF-B-1). Built as B1 increment 1 with D(IS) at PETITION and PUSH and the CAPABILITY field; live with 0.6.0
	\|-		\|-
	\| TPC-PY placed \|\| PRB reads the TPC-PY pages, verifies their digest against the declared index entry, places the module \|\| TPC-PY 0.3.0 declared 2026-10-03; the index entry carries its digest		\| TPC-PY placed \|\| PRB reads the TPC-PY pages, verifies their digest against the declared index entry, places the module \|\| TPC-PY 0.3.0 declared 2026-10-03; the index entry carries its digest
Line 41:		Line 41:
	\| The client contract \|\| Serial requests, maxlag=5, Retry-After obeyed, full-jitter backoff, a descriptive User-Agent naming PRB and the account (D137) \|\| The governor's refusals are stubs on the live TPX; the contract is specification text		\| The client contract \|\| Serial requests, maxlag=5, Retry-After obeyed, full-jitter backoff, a descriptive User-Agent naming PRB and the account (D137) \|\| The governor's refusals are stubs on the live TPX; the contract is specification text
	\|-		\|-
	\| CORROBORATION landing \|\| A REPRODUCTION block names no record; the reproducer pushes the derivation; TPX compares and writes the CORROBORATION record (O-RS-2) \|\| Moved here from M1 by the operator's judgment call J3		\| CORROBORATION landing \|\| A REPRODUCTION block names no record; the reproducer pushes the derivation; TPX compares and writes the CORROBORATION record (O-RS-2) \|\| Moved here from M1 by the operator's judgment call J3; built as B1 increment 3 (the named REPRODUCTION, TPX's comparison, the CORROBORATION with its attested INDEPENDENCE, the NON-CORROBORATION), gated 2026-10-06; obligation O-1, live at criterion (ii)
	\|-		\|-
	\| HOLD and RELEASE \|\| TPX's reaction to a failed canary, scoped by hold_scope; the reserved identifier range for TPX-written records \|\| ~~Moved here~~ from ~~M1 (2026-10-04~~; ~~D247.1~~, D-~~RANGE~~)		\| HOLD and RELEASE \|\| TPX's reaction to a failed canary, scoped by hold_scope; the reserved identifier range for TPX-written records \|\| The reserved range is built as B1 increment 2 (TPX's records from 1,000,001 up; gated 28 of 28, parity 166 of 166); HOLD and RELEASE need a failed canary and are M5's (obligation O-6)
	\|}		\|}

Line 106:		Line 106:
	== How M4 will be tested ==		== How M4 will be tested ==

	* ~~Track B of [[The Principia Machina/Hub/Outside AI\|Outside AI: start here]], the agent's path, once an~~ outside session ~~can hold a bot password~~: the brief hands the session a sponsor-made account and PRB; the session completes one block on a sandbox UWC; the ~~operator reads~~ the ~~chain~~.		* An outside session the operator does not drive: the B1 brief hands the session a sponsor-made account (CH7 AZ, the blue team) and PRB; the session completes one block on the sandbox UWC SPB, and predicts, then attempts, at least eight named refusals (criteria (i) and (iv)).
	* The operator's own run of the ~~same block~~ on the live site, ~~as tpx_land_test.py did for A1 and tpx_a2_test.py for A2~~.		* A REPRODUCTION block worked by a second account of another make, whose match TPX writes as a CORROBORATION record: the first corroboration on the live wiki (criterion (ii), O-1).
	* The builder's recheck of the landed ~~block~~ from outside, read-only.		* The operator's own run of the B1 test script (tpx_b1_test.py, written by the builder) on the live site: the block, the live subset of the fault suite (criterion (iii), O-5), the build line read back (criterion (v)).
	* ~~A planted REPRODUCTION~~ block, ~~blind~~-~~phrased~~, ~~whose match~~ TPX ~~writes as~~ a ~~CORROBORATION~~ record: the ~~first corroboration on the live wiki~~.		* The builder's recheck of the landed blocks from outside, read-only.
			* Before any of it: the A3 closeout, which discharges O-2 and O-4, and the status batch and one M2 session (the order of the user's selection D255.1).

			The fault suite (B1 increment 5) tests five invariants: I1 one holder at a time and a grant never issued twice; I2 no duplicate landing, a non-holder's push lands nothing; I3 a lost answer never changes a committed record's identity or digest; I4 a stale grant lands, releases and extends nothing; I5 a refused request writes nothing. Its scenarios FS-1 to FS-12 cover a duplicate PUSH after a lost answer, a repeated RELEASE, concurrent petition and poll, a delayed PUSH after release and re-grant, a replayed challenge answer, a session cookie invalidated mid-block, HEARTBEAT past the NO-PROGRESS LIMIT, the holder's crash, malformed server answers to PRB, a PUSH carrying a TPX-written field, a VERIFICATION before its TARGET, and citing a REFUTED or HELD record. PRB's LOST-ANSWER RULE: before any re-send it reads STATUS and the chain's last line.

	<graphviz>		<graphviz>
	// M4 on 2026-10-05: ~~nothing started~~; what waits on what.		// M4 on 2026-10-06: Step B open; what waits on what.
	digraph m4status {		digraph m4status {
	rankdir=LR; node [shape=box, style=filled, color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=9]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];		rankdir=LR; node [shape=box, style=filled, color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=9]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];
	F [label="~~Step A findings closed~~\~~nG-6, G-7 retest~~;\nF-~~VIEW-1~~, F-~~TPCRUN-1,~~\~~nF-STATUS-1 in 0.5.x~~", fillcolor="#ffedad"];		F [label="A3 closeout\nstatus batch 0.1.3 imported;\nthe runner: O-2, O-4;\none M2 session", fillcolor="#ffedad"];
	BR [label="~~the Step B~~ brief~~\nwritten by the operator~~", fillcolor="#~~eaecf0", style="filled,dashed~~"];		BR [label="B1 built\ninc 1 to 3 gated 2026-10-06;\ninc 4, inc 5, PRB 0.1.0;\nthe B1 brief", fillcolor="#cedff2"];
	M4 [label="M4 PRB\~~nNOT STARTED~~", fillcolor="#~~eaecf0", style="filled,dashed~~", fontsize=10];		M4 [label="M4 PRB\nUNDER WAY\n\"B1 PASSED\" needs (i)-(vi)\nand O-2, O-4 discharged", fillcolor="#ffedad", fontsize=10];
	M5 [label="M5 certification\nNOT STARTED", fillcolor="#eaecf0", style="filled,dashed", fontsize=10];		M5 [label="M5 certification\nNOT STARTED (B2)", fillcolor="#eaecf0", style="filled,dashed", fontsize=10];
	F -> BR -> M4 -> M5;		F -> M4; BR -> M4; M4 -> M5;
	}		}
	</graphviz>		</graphviz>

DeltaS Zero: M4: the diagrams re-laid out to fit the content column (tpm_testing 0.1.1)

2026-10-06T00:47:54Z

M4: the diagrams re-laid out to fit the content column (tpm_testing 0.1.1)

← Older revision	Revision as of 00:47, 6 October 2026
(No difference)

BFP Rauch: 1 revision imported

2026-10-06T00:47:34Z

1 revision imported

← Older revision		Revision as of 00:47, 6 October 2026
Line 12:		Line 12:
	// Where PRB sits: between the model's session and TPX's API.		// Where PRB sits: between the model's session and TPX's API.
	digraph prbplace {		digraph prbplace {
	rankdir=LR; node [shape=box, style=filled, fillcolor="#eaecf0", color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=10]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];		rankdir=TB; node [shape=box, style=filled, fillcolor="#eaecf0", color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=10]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];
	H [label="the human\n(sponsor; runs PRB)"];		H [label="the human\n(sponsor; runs PRB)"];
	M [label="the model's session\n(a CA-GTP, later;\nin M4 any session)", fillcolor="#ffedad"];		M [label="the model's session\n(a CA-GTP, later;\nin M4 any session)", fillcolor="#ffedad"];

BFP Rauch: 1 revision imported

2026-10-06T00:26:44Z

1 revision imported

← Older revision	Revision as of 00:26, 6 October 2026
(No difference)

DeltaS Zero: M4: PRB, the smallest client; Step B; not started; what moved here from Step A (tpm_testing 0.1.0)

2026-10-06T00:26:37Z

M4: PRB, the smallest client; Step B; not started; what moved here from Step A (tpm_testing 0.1.0)

New page

{{TPM map}}
{{DISPLAYTITLE:Testing M4: PRB, the smallest client}}
''Phase M4 of [[The Principia Machina/Testing|Testing the Principia Machina]]. State: NOT STARTED. Grouped with M5 as Step B by decision D237.1 (2026-10-03); it opens once Step A's findings are closed and the Step B brief is written. The items moved out of Step A – CORROBORATION landing, HOLD and RELEASE, the reserved identifier range – land here.''

== Objective ==

The plan (tpm_third_party_plan 0.2.0, section 4) states M4 as ''PRB, the smallest client that drives TPX through its API''. PRB is the agent-side program described in [[The Principia Machina/TPS/5.4 PRB|the specification]]: it signs in with the agent's bot password, petitions for a lock, polls, pushes records, returns a coworker's work, releases the lock, and carries the published calculator (TPC-PY) so that every value an agent presents was computed, never reasoned. M4 builds the least PRB that completes one block on the live wiki and tests it against the TPX that Step A left running.

The plan's acceptance: one full block – petition, lock, push, release – completed from a session the operator did not drive, every presented digest recomputed equal by TPX at landing, and the execution challenge answered from executed code.

<graphviz>
// Where PRB sits: between the model's session and TPX's API.
digraph prbplace {
rankdir=LR; node [shape=box, style=filled, fillcolor="#eaecf0", color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=10]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];
H [label="the human\n(sponsor; runs PRB)"];
M [label="the model's session\n(a CA-GTP, later;\nin M4 any session)", fillcolor="#ffedad"];
PRB [label="PRB\nthe client\nnot yet built", shape=box3d, fillcolor="#ffedad", style="filled,dashed"];
PY [label="TPC-PY 0.3.0\nplaced by PRB\nexecuted, never reasoned"];
API [label="api.php\naction=tpx"];
TPX [label="TPX 0.5.0\nlive since 2026-10-05", shape=box3d, fillcolor="#cedff2"];
W [label="the wiki\nSPR register, chains"];
H -> PRB [label="starts"]; M -> PRB [label="records, requests"]; PRB -> PY [label="computes with"]; PRB -> API [label="PETITION, POLL,\nPUSH, RETURN, RELEASE"]; API -> TPX -> W;
}
</graphviz>

== What M4 has to build ==

{| class="wikitable"
! Piece !! What the specification asks !! Where it stands on 2026-10-05
|-
| Sign-in || A bot password made by the sponsor at Special:BotPasswords, with the grants the client needs (D228.1) || The grants are listed in the PRB client specification (C-20); no PRB exists
|-
| The block || PETITION, then POLL until the lock is granted, PUSH, RELEASE; HEARTBEAT within the NO-PROGRESS LIMIT || TPX's side exists and was driven by the operator's scripts in A1 and A2
|-
| The challenge || At petition and on every push TPX issues a 128-bit nonce; PRB answers digest_fields(["TPC-EXECUTION-CHALLENGE", "1", nonce]) from executed code || TPX's side exists; the operator's scripts answer it from the published calculator
|-
| TPC-PY placed || PRB reads the TPC-PY pages, verifies their digest against the declared index entry, places the module || TPC-PY 0.3.0 declared 2026-10-03; the index entry carries its digest
|-
| record_check at PUSH || PRB's advisory pre-check of every record against the record table before the push || The function exists in both residences (tpc_record 0.1.0)
|-
| The client contract || Serial requests, maxlag=5, Retry-After obeyed, full-jitter backoff, a descriptive User-Agent naming PRB and the account (D137) || The governor's refusals are stubs on the live TPX; the contract is specification text
|-
| CORROBORATION landing || A REPRODUCTION block names no record; the reproducer pushes the derivation; TPX compares and writes the CORROBORATION record (O-RS-2) || Moved here from M1 by the operator's judgment call J3
|-
| HOLD and RELEASE || TPX's reaction to a failed canary, scoped by hold_scope; the reserved identifier range for TPX-written records || Moved here from M1 (2026-10-04; D247.1, D-RANGE)
|}

<graphviz>
// The block PRB has to complete, as the live TPX serves it.
digraph block {
rankdir=TB; node [shape=box, style=filled, fillcolor="#eaecf0", color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=9]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];
S [label="sign in\nbot password (D228.1)", fillcolor="#cedff2"];
P [label="PETITION\ncapability: execution mode,\nD(IS), D(PROMPT), the challenge"];
Q [label="the queue\none WAITING petition\nper account per UWC"];
L [label="the lock\ngrant number = fencing token;\nexpiry at most 24 h"];
W [label="work\nrecords prepared;\nrecord_check at PUSH\nwith executed TPC-PY"];
U [label="PUSH\nthe grant, the records,\nthe challenge answered"];
X [label="TPX lands or refuses\nrecomputes every digest;\nthe screen runs", fillcolor="#cedff2"];
R [label="RELEASE\nvalid only after a push;\nthe badge written last"];
S -> P -> Q -> L -> W -> U -> X -> R; X -> W [label="refused:\nfix and push again", style=dashed]; L -> L [label="HEARTBEAT\nwhile progress continues"];
}
</graphviz>

== How the block runs, call by call ==

{{#mermaid:
sequenceDiagram
participant S as sponsor
participant P as PRB
participant T as TPX
participant W as wiki pages
S->>P: start a session
P->>W: read TPC-PY pages
P->>P: verify digest, place TPC-PY
P->>T: PETITION (capability, D(IS), challenge answer)
T-->>P: WAITING, then ASSIGNED, grant n
P->>T: HEARTBEAT
P->>P: record_check at PUSH
P->>T: PUSH (grant n, records, challenge answer)
T->>T: recompute digests, run the screen
T->>W: write records, chain line, badge last
T-->>P: LANDED, next id
P->>T: RELEASE (grant n)
T->>W: lock cleared, badge
T-->>P: RELEASED
|config.theme=neutral}}

== What moved here from Step A ==

<graphviz>
// Items the operator moved out of Step A into Step B (2026-10-03 to 2026-10-05).
digraph moved {
rankdir=LR; node [shape=box, style=filled, fillcolor="#eaecf0", color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=9]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];
A [label="Step A\nTPX part 2, live", fillcolor="#cef2e0", fontsize=10];
B [label="Step B\nM4 PRB and M5 certification", fillcolor="#ffedad", fontsize=10];
C [label="CORROBORATION landing\nTPX compares a reproduction,\nwrites the record (O-RS-2)\njudgment call J3"];
H [label="HOLD and RELEASE\nhold_scope, held_closure,\nthe HOLD and RELEASE records\n2026-10-04"];
R [label="the reserved range\nTPX-written records from\nits own identifier range\nD247.1, D-RANGE"];
K [label="the lock's stub refusals\nthe governor's lanes and seats\nD-LOCK"];
A -> C -> B; A -> H -> B; A -> R -> B; A -> K -> B;
}
</graphviz>

The reasoning was the operator's judgment call J3 of 2026-10-04: a corroboration is written by TPX from a reproduction it commissioned, so it belongs with the canary and parrot path that M5 builds, not with the register screen; HOLD and RELEASE are the reaction to a failed canary and need the same path. A1 and A2 carried the screen, the withdrawals, promotion and verification instead.

== How M4 will be tested ==

* Track B of [[The Principia Machina/Hub/Outside AI|Outside AI: start here]], the agent's path, once an outside session can hold a bot password: the brief hands the session a sponsor-made account and PRB; the session completes one block on a sandbox UWC; the operator reads the chain.
* The operator's own run of the same block on the live site, as tpx_land_test.py did for A1 and tpx_a2_test.py for A2.
* The builder's recheck of the landed block from outside, read-only.
* A planted REPRODUCTION block, blind-phrased, whose match TPX writes as a CORROBORATION record: the first corroboration on the live wiki.

<graphviz>
// M4 on 2026-10-05: nothing started; what waits on what.
digraph m4status {
rankdir=LR; node [shape=box, style=filled, color="#a2a9b1", fontcolor="#202122", fontname="Helvetica", fontsize=9]; edge [fontname="Helvetica", fontsize=9, color="#54595d", fontcolor="#202122"];
F [label="Step A findings closed\nG-6, G-7 retest;\nF-VIEW-1, F-TPCRUN-1,\nF-STATUS-1 in 0.5.x", fillcolor="#ffedad"];
BR [label="the Step B brief\nwritten by the operator", fillcolor="#eaecf0", style="filled,dashed"];
M4 [label="M4 PRB\nNOT STARTED", fillcolor="#eaecf0", style="filled,dashed", fontsize=10];
M5 [label="M5 certification\nNOT STARTED", fillcolor="#eaecf0", style="filled,dashed", fontsize=10];
F -> BR -> M4 -> M5;
}
</graphviz>

Previous: [[The Principia Machina/Testing/M3 TPX, the smallest server|M3]]. Next: [[The Principia Machina/Testing/M5 Certification|M5]]. Back to [[The Principia Machina/Testing|Testing the Principia Machina]].

[[Category:The Principia Machina]]