Inputs: register records

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 kernel above, the register below: records are checked against both. (diagram page.)

Purpose

How work reaches the register, and what a register record carries.

Explains: TPS 0.3.0 (declared final on 2026-09-28 at revision 6), which carries the register in 3.1 to 3.4 and landing in 5.9; with the initial and boundary values of D180.3 from revision 6; TPC-PY 0.1.0 (declared on 2026-09-28, tree digest a00161c1b321fd66abc591209007d46a7fa6290097835060e50f381426259043, conformed TPS 0.3.0; tpc_zone 0.5.0, tpc_units 0.1.1, tpc_tests 0.2.0, tpc_form 0.2.0, tpc_eom 0.1.0; schema 0.5.0) with check_draft 0.5.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. The RR input buffer is part of the Recorder UI TPX provides. The record schemas - the field list with types - are owed: the master record, assumption, entry-status, withdrawal and corroboration records (C-13), the named-gap record (C-15), the verification record (C-07), and the record field schema (C-16). This page explains the path and the fields the rules already name.

The path

No person and no agent writes the register directly. Work enters by one route (TPS 5.4 and 6.4):

1. a user puts work into the RR input buffer in the Recorder UI;
2. TPX passes it to a certified agent (CA-GTP) working the UWC;
3. the agent does the work and asks TPX to add a record, amend one, or change a record's status;
4. TPX checks the request and, at landing, writes the register.

An agent reads register records; it does not write them. The agent that holds the UWC's lock is the lead: only it may ask TPX to allocate record identifiers.

What a record carries

Every record is identified as prefix-n, the prefix unique to the UWC (TPS 3.1). The fields the strike rule already names (TPS 3.2):

FINDING

the claim, tested against the TFK.

ASSUMPTIONS

the identifiers of the assumption records it rests on beyond the TFK. Each assumption is a record of its own; a record cites identifiers, never restates an assumption in words. An interaction the TFK leaves out - a friction, a field - enters a result only this way, as its own assumption record: it extends the world of that record and of the records that cite it, never the TFK's (TPS 2.2.19).

REGIME

L for a result checkable by re-derivation with no measured input; M for a measured value with its uncertainty.

DERIVATION

the steps, counted under the UWC's STEP_CONVENTION.

DOMAIN

where the result holds; required on every record that promotes.

For an M record

VALUE, its combined standard uncertainty with the Type B components listed, QUANTITY - the NAME of the TrM entry the value belongs to - and UNIT, which must have that entry's dimension. Before comparing two values TPX converts both to SI units; a pair whose units differ in kind, such as Hz against rad s-1, is not compared but opens an audit block (see Text and numbers).

Records that the machine fills - corroboration's INDEPENDENCE, the SAME-MODEL mark, the master record - are never entered by hand.

Promotion

A result is promoted only when its falsifier's class reaches the UWC's PROMOTION_FLOOR (the Measure Set) and its other conditions are met. Corroboration does not gate promotion (record D92.1; TPS 3.2.12). An initial or boundary value a result relies on - where a mass starts, say - is its own ASSUMPTION record, cited in that result's ASSUMPTIONS (TPS 3.2.15; D180.3).

EOM-0, a first task

A UWC declared with STRUCTURE_CHECK ON whose structure check found a DOF that no law determines opens with the objective EOM-0 (TPS 3.3.16). While it is OPEN, TPX lands pushes only from blocks of kind EOM-0 or REPRODUCTION. The missing equation is settled by a standing L record that derives it from the TFK in a declared form, by an assumption record that supplies it, or by the declaring authority's declaration that the gap stands. An initial value's assumption record settles nothing. Until the record field schema is written (C-16), the lead names the settling record in the push, and TPX records that naming as an inspection.

External values

A derivation never aims at a known value. A comparison with an outside value is made after the run and lands as a verification record, regime M, reporting the difference, never the agreement (TPS 3.3).

Non-goals

The buffer is not a way to change the TFK. A request to change the kernel is redirected to the new-container form (TPS 5.5).

Worked example

In the spring UWC a user asks for the period of oscillation. A certified agent derives 2 pi sqrt(m / k_s) from EOM_X and KIN, the kernel's equations of motion. The kernel's own assumptions, A_kpos and A_mpos, are part of the TFK and are not cited, so the record's ASSUMPTIONS is empty, and the agent asks TPX to add an L record. A second request, where the mass is one second later, needs where it started: the agent cites two assumption records, x = 1 cm at t = 0 and v = 0 at t = 0, and its finding holds under those values only (TPS 3.2.15). Later a measured period is compared against the first result in a verification record, regime M, with QUANTITY naming the relevant TrM entry, and the difference is reported.

Governing sections: TPS 3.1, 3.2, 3.3, 5.4 and 6.4.

---

Previous: The access list. Next: Collaboration and the lock.