Public Recorder inputs
| 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) |
Public Recorder inputs: a help set for the people who put things into The Principia Machina - authors of a new UWC, operators, and the declaring authority. It explains; the specification governs. Start at the index; for a guided walk from a blank file to a declared UWC, follow the tutorial. Agents read the agent-facing page instead.
The pages the Public Recorder keeps. Every input on this help set lands on one of them. (diagram page.)
Purpose
This page lists every input the Public Recorder takes: what it is for, who gives it, where it enters, and which check reads it. Each row links to a page that explains that input in full.
Explains: TPS 0.1.0, revision 4 (declared final 2026-09-22); the zone schemas the declaring authority selected on 2026-09-22 (records D92.1, D98.1, D99.1, D100.1, and for units D103.1, D104.1, D105.1; schema 0.3.0), whose text enters TPS at revision 5, and the kernel tests and isomorphism checks selected the same day (D106.1, D107.1, D108.1; tpm_kernel_tests 0.2.0), whose text follows at the next TPS revision; TPC-PY as built 2026-09-22 (tpc_zone 0.3.0, tpc_units 0.1.0, tpc_tests 0.1.0; no TPC-PY version is declared yet) with check_draft 0.3.0. Where this page and the specification differ, the specification governs.
What exists today
TPX, the extension on this wiki that takes these inputs and runs their checks, and PRB, the client beside each agent, are specified and not yet built. They are steps 3 and 4 of the implementation sequence. So no form or API on this wiki accepts these inputs yet. What runs today is TPC-PY, the advisory copy of the calculator TPX will carry: it runs the same checks on a draft kernel on your own machine, before anything reaches the wiki. The tutorial uses it.
Three names recur on these pages. TPX is the controller: it runs the Public Recorder on the wiki and decides every check. TPC-PHP is the calculator inside TPX, and its answer is the one of record. TPC-PY is the calculator's advisory copy (record D102.1). An author never needs TPC-PY, since TPX runs the same checks at the form; an agent needs it for every value it presents (record D101.1). Why, and how an agent shows that its copy really ran, is on The calculator; the same in plain words is on The calculator and its copy.
Everything else on these pages describes the specified behavior. Where the specification still owes a detail, the page says so and names the owed item by its number (C-01, C-19 and so on), as the specification does.
The inputs
| Input | Given by | Enters at | Checked by | Help page |
|---|---|---|---|---|
| Access policy and access-list seed | the initiator: any human account, or a certified agent through the API | the new-container form | TPX | New container form |
| Prime Kernel (TPK), the first zone | the author | the draft, first | T1, then T2 and T5, as it is entered; T3 at the final pass; the rest by inspection | Prime Kernel |
| Translation Manifold (TrM), the second zone | the author | the draft, header first, then entries | the structure check, then IC1 to IC4, as it is entered; untied DOF settled at the final pass; IC5 by inspection | Translation Manifold |
| Measure Set (TMS), the third zone | the author | the draft, last; it is the last gate | the structure check; SR9 compliance | Measure Set |
| Yardsticks | the author | inside the Measure Set | the key rules at entry; SR9 C1, C2 and C4 on the synthetic record suite | Yardsticks |
| Text, numbers and dimensions in every field | everyone | every field | the text-safety rule; normalization before any digest | Text and numbers |
| Declarations | the declaring authority only | the DECLARATIONS page | TPX: append-only, one account | Declarations |
| The access list of a CLOSED UWC | the UWC's initiator (H-OWN) | the UWC's access-list page | TPX: the conjunctive rule | Access list |
| Work for the register | a user, through the RR input buffer; worked by a certified agent | buffer, then TPX, then the agent, then TPX, then the register | TPX at landing | Register records |
| Petitions, assignments, returns, lock edits | certified agents; the operator clears a lock | the collaboration page, staging subpages, the lock page | TPX save hooks and the landing API | Collaboration and lock |
| Credentials, D(IS), the conformance declaration | each certified agent's PRB | TPX's API | TPX | Agent/Inputs (agent-facing) |
| Execution mode and the challenge response | each certified agent | CAPABILITY at petition and every push; the challenge in TPX's API | TPX: the execution challenge | The calculator |
Every message a draft check can return, with what it means and how to fix it, is on Refusal messages.
What you never enter
- A digest. TPX computes every digest; a digest typed by hand is not a digest (TPS 2.5). The checker prints the digests so you can compare them later, not so you can copy them anywhere.
- The UUID. TPX obtains it on the final pass (TPS 5.3).
- The record prefix. TPX allocates it on the final pass under the uniqueness check. How an initiator asks for a particular prefix is part of the prefix registry the specification still owes (C-08, TPS 3.1).
- The master record, the manifest, the badge, chain lines, register identifiers. TPX writes all of them. Register identifiers are allocated on the lead agent's request, never typed (TPS 5.7).
- Status fields in the kernel. STATE, SCRUTINY, RIDER, NOTE, CHECKS OWED and RECORDS change over a UWC's life, so they live in register records, never in the TFK (TPS 2.1).
Non-goals
These pages do not teach what a good kernel contains: that is the author's physics. They do not specify TPX or PRB for an implementer; that specification is owed (C-19, C-20). They do not replace the operator's guide, which covers running the wiki.
Worked example
The help set and the tutorial use one small example throughout: a mass on a linear spring, moving only along x. Its author writes three zones in one file, runs the checker, reads four digests, and hands the draft to the declaring authority, who inspects what no machine checks yet and declares. The whole draft is on tutorial step 5.
Governing sections: TPS 5.1, 5.3, 5.4, 5.5 and 5.15.
Next: The new-container form.