3.2 Record fields and regime (TPS 0.5.0)
Instruction artifact, machine-optimized text: TPS, section 3.2 Record fields and regime. Part of TPS and the TPM hub. Human-only edit (TPS 5.13). TPS 0.1.0 was declared final at revision 4 on 2026-09-22, a version declaration recorded in the foundations record; the chain begins at TPX's first landing (TPS 5.6.7). TPS 0.1.1, which changed only the status lines, was declared final on 2026-09-26, TPS 0.3.0, revision 6, on 2026-09-28, and TPS 0.4.0, revision 7, on 2026-09-30. This page is revision 8 of the tree, proposed as version 0.5.0 until H-DECL declares it; revision 7 is carried whole, and revision 5, proposed as 0.2.0, stays undeclared. The text below is this section of the TPS artifact at 0.5.0 (proposed), verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.
TPS 3.2 RECORD FIELDS AND REGIME
purpose: the record field schema, the closed table tpm_record_schema;
regime L or M assigned at allocation; GRADE and STATUS, HELD;
the unit grammar and KIND; the promotion floor; LITERATURE;
initial and boundary values and CONDITIONS; the envelope, the
classes, the RESULT's fields, the record digest, the check and
the views
governs: 3.2 | version: 0.5.0 (proposed) | class: instruction artifact
audience: operator, agent
3.2.1 Record fields the strike rule needs: ASSUMPTIONS, REGIME,
DERIVATION, and for M records VALUE with u_c and its Type B list.
The record field schema is the closed table tpm_record_schema
0.4.0 (3.2.16-3.2.21). [B-14] [C-16] [D192.2]
3.2.2 A RESULT carries a FINDING, its STATEMENT with any declared form
(EQUATION on an L record; QUANTITY, VALUE and UNIT), tested
against the TFK by the strike rule (see 4.4); every record
carries a GRADE, written at landing as 5.9 and, for an inherited
record, 3.4.2 state (3.2.10). [I-068] [B-04] [B-11] [D193.2]
[D195.3] [D215.2]
3.2.3 DOMAIN and DOMAIN_CONDITION are required on every promoting
record (see 2.3.3). A promoting record is a standing RESULT
meeting the conditions of 3.2.12; promotion writes nothing on the
TrM entry, whose state is the ENTRY VIEW (3.3.2). [I-030]
[D197.2] [D201.1]
3.2.4 REGIME. Each record is assigned one regime at allocation. L: the
FINDING is verifiable by re-derivation from the TFK plus
ASSUMPTIONS with no empirical input. M: the FINDING carries a
value with a combined standard uncertainty u_c per GUM (JCGM
100:2008, see 8.3). A record comparing an L result with an
external value is M, of the verification class. [I-070] [I-035]
3.2.5 Every M RESULT states U_C, positive, and BUDGET, a non-empty list
of every component {NAME, U, UNIT, EVALUATION A or B, BASIS},
SR8's Type B list among them, with CORRELATED, false when absent
(see 4.4, SR8). TPX checks at landing that U_C is the root sum of
squares of the components, normalized to U_C's UNIT, at U_C's
last written digit, MECHANICAL (TPC budget_check), the record
digest keeping that digit (3.2.20); a correlated budget, or a
component whose UNIT is not a power-of-ten multiple of U_C's, is
INSPECTION. [I-075] [D195.3]
3.2.6 Regime assignment is INSPECTION at allocation, MECHANICAL when
derivations are formal. A record lacking the fields a(r) and s(r)
are computed from, ASSUMPTIONS, CITES and DERIVATION.STEPS (an
integer from 1 under the STEP CONVENTION), is refused on write
(see 4.2, rows 19 and 22). [B-18] [D195.3]
3.2.7 ASSUMPTIONS cites ASSUMPTION RECORD identifiers only; an
assumption is never restated in free text (see 3.3.7).
ASSUMPTIONS and CITES are required on every class that carries
them, possibly empty; CITES names RESULT identifiers only; TPX
refuses a member that is not a standing record of the UWC of the
right class (4.4.9). [D41.2] [D192.2] [D194.1]
3.2.8 An M RESULT states QUANTITY and UNIT with its VALUE, U_C and
BUDGET, its QUANTITY among its ENTRIES when ENTRIES is given; an
L RESULT may carry QUANTITY, VALUE and UNIT together for a
derived value, never U_C or BUDGET; both carry AT where the value
holds at a point (3.2.15). QUANTITY is the TrM entry the value
belongs to. [D40.1] [D195.3] [D196.1]
3.2.9 An L record whose derived value enters an L-M test states
QUANTITY and UNIT for that value; otherwise the test is refused
(see 4.4, SR3). UNIT is written in the unit grammar of 3.2.11; on
write TPX parses it and checks its dimension against the QUANTITY
entry's DIMENSION, refusing a record whose UNIT does not parse or
does not match (4.2, row 55). The resolution of QUANTITY to an
entry of the UWC's TrM and the unit's dimension check are
record_check's at the stage LANDED (3.2.21). [D40.1] [D103.1]
[D192.2]
OWED: TPX's running of that check, at build step 3; kind:
computation; C-32.
3.2.10 STATUS AND GRADE (D111.1, D193.2). Every register record carries
a GRADE, written by TPX at landing and never rewritten in place,
inside the RECORD DIGEST: PROVISIONAL on RESULT, ASSUMPTION,
CORROBORATION and VERIFICATION; NOT GRADED on MASTER, NAMED_GAP,
WITHDRAWAL, PROMOTION, ENTRY_STATUS, HOLD and RELEASE. A later
grade is set by the new record that carries it: a PROMOTION
record sets ESTABLISHED (3.2.12); a WITHDRAWAL record sets its
status_set, REFUTED or WITHDRAWN, on the withdrawn record and
WITHDRAWN on each cascade member (3.3.3). A record's current
grade is computed and TPX's reading view shows it. The five
classes an account authors carry STATUS, written by TPX in place
and never by a CA-GTP (5.4.7), outside the digest: UNMARKED at
landing, HELD, or REFUTED, the strike's mark, which a WITHDRAWAL
of cause INHERITED setting REFUTED also writes (3.3.14, 3.4.2);
TPX's classes carry none. HELD is never a GRADE. HELD is written
by TPX into every record it holds after a failed canary (5.14
CR6), so a reader of that record alone sees it; the prior status
kept in the HOLD record is the record's status word, its STATUS
when HELD or REFUTED and otherwise its current grade, and is
restored on release (3.3.11-3.3.13). A record stands when its
status word is PROVISIONAL or ESTABLISHED (SR2, 4.4.9). [D111.1]
[D193.2] [D215.2]
3.2.11 UNIT GRAMMAR (D103.1). UNIT is "1" or space-separated tokens,
each [prefix]symbol[exponent], in the DIMENSION field's shape
("kg m s-2"), over a closed catalogue: m g s A K mol cd; rad sr;
Hz N Pa J W C V F Ohm S Wb T H lm lx Bq Gy Sv kat; min h d au deg
arcmin arcsec ha L t eV. Refused with reasons: degC (an offset),
Da (a measured value), Np, B and dB (logarithmic). The 24 SI
prefixes, micro written u; no prefix on min, h, d, ha, au, deg or
arcmin. The canonical spelling is what every preimage carries
(2.5.11). The scale to coherent SI is computed in one fixed order
of double operations, so both residences agree byte for byte. No
imperial, CGS or natural unit and no UCUM interchange (7.1). UNIT
is checked for its dimension, not its size: a value meant in m
and written in km passes. KIND, what a dimension cannot see, is
stated at 4.4.11. The text is tpm_units 0.2.3; the functions and
their vectors are in both residences (5.1.5). C-32 refuses a
DIMENSION whose bases sum past the bound of 2.5.12 with its
reason. [D103.1] [D105.1] [S15]
3.2.12 PROMOTION (D92.1). A RESULT is promoted only when its falsifier's
class, the lower of the RESULT's own FALSIFIER_CLASS and that of
every TrM entry in its ENTRIES (2.3.11), reaches the UWC's
PROMOTION_FLOOR, a TMS parameter declared at instantiation and
tested at CAC under SR9 C5, F2 where the UWC does not say
otherwise (2.4.5). Corroboration does not gate promotion; CR7 and
SR6's independence count are unchanged. A UWC that declares F1
weakens only itself. A HELD record is not promoted while held
(4.4.9). TPX promotes a standing RESULT, never a VERIFICATION or
an ASSUMPTION, to ESTABLISHED at the landing that makes it
eligible, mechanically (TPC promotion_eligible and
promotion_pass), when DOMAIN and DOMAIN_CONDITION are stated,
ENTRIES is not empty, the class read reaches the floor,
DERIVATION.STEPS is at least 1, every RESULT in its CITES is
ESTABLISHED, no audit block is open on it or on a record of its
closure, and it is not HELD; promotions propagate to a fixed
point in the same landing, and one PROMOTION record per promoting
landing records them (3.3.17). [D92.1] [D111.1] [D197.2] [D201.1]
3.2.13 STATUS IN THE RECORD (D140.1; D111.1 kept whole). TPX writes a
record's status (its STATUS: HELD; on release UNMARKED, HELD or
REFUTED; REFUTED on a strike or a WITHDRAWAL of cause INHERITED
setting REFUTED) and a NAMED_GAP's STATE line, GRADE never being
rewritten in place, into the record's own text, a FROZEN volume
included, and nothing else there, so a raw-wikitext reader sees
the status too. A status write rewrites that volume's path in the
MANIFEST TREE (5.11.11). [D140.1] [D111.1] [D193.2] [D199.1]
[D215.2]
3.2.14 LITERATURE (D171.1 (g)). The record field schema (3.2.1,
tpm_record_schema 0.4.0) carries LITERATURE: the BIB IDs of the
BIBLIOGRAPHY ENTRIES the record relies on (5.21.10); a
verification-class M record (3.2.4, 3.3.6) names there the entry
its external value comes from. On write TPX refuses a member that
is not a landed entry of the same UWC, so entries land before the
records that cite them (5.4.14); a superseded entry stays
citable. Under a BIBLIOGRAPHY SETTING OFF the record has no
LITERATURE field. A LITERATURE member is not a citation of a
record: it enters no ASSUMPTIONS closure, no d(r) and no held
closure (4.4.12). A VERIFICATION's SOURCE is a BIB ID in its
LITERATURE under ON or CLOSED (3.3.6). [D171.1] [D192.2] [D200.1]
3.2.15 INITIAL AND BOUNDARY VALUES IN THE REGISTER (D180.3). Each
initial or boundary value a record relies on is its own
ASSUMPTION record, cited in the record's ASSUMPTIONS and so
priced in a(r) (4.4.5). A FINDING about a trajectory is
conditional on the values it cites: two such FINDINGS under
different values do not contradict. A structured initial or
boundary value is a SITUATION ASSUMPTION record: SITUATION
(INITIAL or BOUNDARY), DOF, VALUE, UNIT against the DOF's
DIMENSION, and AT, the point where the value is given, declaring
no ROLE; a value in prose only stays an ordinary ASSUMPTION, row
23's inspection. An M record, and an L record whose derived value
enters an L-M test, carries AT, the point at which its value
holds, possibly empty. CONDITIONS is computed by TPC
(conditions_of), never declared: the sorted identifiers of the
SITUATION records in the record's ASSUMPTIONS closure, and its AT
normalized to coherent SI in the canonical decimal form, sorted
by DOF. [D180.3] [D196.1]
3.2.16 THE RECORD TABLE (D192.2). The closed table tpm_record_schema
0.4.0 fixes every register record's form: per CLASS each field,
required or optional, of one type class of a closed list, RID,
IDSET, IDENT, TEXT, DECIMAL, UNIT, DIMENSION, FORM, PREDICATE,
ENUM, INT, BOOL or OBJECT, each defined by the TPC function or
canonical form that checks it; its cardinality a column. A field
the table does not name is refused, never dropped (2.2.11). TPS
states the rules; the table is their specification text, as
tpm_units is 3.2.11's. [D192.2]
3.2.17 THE ENVELOPE (D192.2, D193.2). Every keyed record opens with ID;
CLASS; GRADE (TPX, at landing); STATUS (TPX, in place); BLOCK and
AUTHOR (TPX, from the push: the coworker's block and account for
a record a RETURN carried); LANDED_BY and LANDED (TPX); VETTED_IN
(TPX, the lead's incorporating block); CITES and ASSUMPTIONS
(required, possibly empty); LITERATURE (under a BIBLIOGRAPHY
SETTING ON or CLOSED only); SUPERSEDES; INHERITS (TPX, on a
record a COPY-FORWARD writes); TPS and D_IS (TPX, from the push);
DIGEST (TPX, 3.2.20). A field TPX writes is refused at the push.
D(TFK) is not repeated per record: the MASTER carries it and the
digest gate runs before every write (2.5), a divergence from the
guide's L2.4 recorded under its 2.5. [D192.2] [D193.2]
3.2.18 THE CLASSES (D192.2). CLASS is one of RESULT, ASSUMPTION,
CORROBORATION, VERIFICATION, WITHDRAWAL, NAMED_GAP, ENTRY_STATUS,
PROMOTION, MASTER, HOLD, RELEASE; block kinds and release kinds
are not classes. RESULT, ASSUMPTION, CORROBORATION, VERIFICATION
and ENTRY_STATUS are pushed by a lead and checked at the push and
again at landing, except a CORROBORATION TPX writes on a ledger
or a PARROT's MATCH (3.1.11), checked at landing only; NAMED_GAP
and MASTER are written by TPX alone and checked at landing; HOLD,
RELEASE, WITHDRAWAL and PROMOTION are TPX's positional lists,
each with its own digest form and TPC functions (3.3.3, 3.3.11,
3.3.12, 3.3.17). The fields of each keyed class are the table's:
ASSUMPTION 3.3.7, CORROBORATION 3.3.4, VERIFICATION 3.3.6,
ENTRY_STATUS 3.3.2, NAMED_GAP 3.3.5, MASTER 3.3.1, RESULT 3.2.19.
[D192.2]
3.2.19 THE RESULT'S FIELDS (D195.3, D197.2, D198.1, D201.1). STATEMENT,
prose, required; REGIME, L or M (3.2.4); DERIVATION {STEPS, an
integer from 1 under the STEP CONVENTION; TEXT, the exhibited
steps}; FALSIFIER, prose, and FALSIFIER_CLASS, F1 to F3,
required; DOMAIN, prose, and DOMAIN_CONDITION, optional at
landing and required for promotion (2.3.3); REFS, TPK DOF and
CONSTANT names, required with EQUATION or DOMAIN_CONDITION;
EQUATION, a form in the TPK grammar (2.2.13), on an L record
only, and ROLE, one of the LAW roles of 2.2.6, only with EQUATION
(3.3.16); ENTRIES, TrM entry names, required for promotion;
QUANTITY, VALUE, UNIT, U_C, BUDGET and CORRELATED on an M record
(3.2.5, 3.2.8), QUANTITY, VALUE and UNIT on an L record's derived
value; AT (3.2.15). Prose against a declared form stays
INSPECTION. [D195.3] [D197.2] [D198.1] [D201.1]
3.2.20 THE RECORD DIGEST (D192.2, D193.2). A keyed record's digest is
digest_fields (2.5.10) over ["TPC-RECORD", "1", n, then each
field of its class present or defaulted, in the table's order, as
its name and its value], n the count of those fields: a flat list
of names, values and counts, with no type tag, the names, the
counts and the table's order making it unambiguous. Values in the
canonical forms of 2.5.11 and 2.5.12, a RESULT's U_C in its
precision form instead: its digits as written from the first
non-zero one to the last, trailing zeros kept, with the exponent
of the last (TPC prec_decimal; "0.0010", "1.0e-3" and "10e-4" are
"10e-4", "1e-3" and "0.001" are "1e-3"); a set, or a list of
objects, as its member count and its members sorted; an object as
its count of fields and each field's name and value; defaults
emitted; the ID and GRADE inside; STATUS, DIGEST and a
NAMED_GAP's STATE line outside. TPX computes it at landing (TPC
record_digest; record_preimage its list) and writes it into the
record's text; it is the COMMUNITY LEDGER's TARGET digest
(5.9.13). The table's tpm_record_schema 0.4.0 section 9 is the
preimage's full statement. [D192.2] [D193.2]
3.2.21 THE CHECK AND THE VIEWS (D192.2). TPC record_check checks a
record against the table at the stage PUSH (the author's and the
lead's fields, TPX's absent), PRB's advisory pre-check with
executed TPC-PY (5.4.23), and at the stage LANDED, after TPX has
written its fields, TPX's check of record with TPC-PHP; a refusal
names a stable code, REC-01 onward, the field and a fixed
message, reported alike by TPX and PRB. The canonical spelling on
the wire, on the pages and in TPC's readers is upper case; the
modules that read records keep their own shapes behind one
function, record_view, whose eight views are HOLD, STRIKE, SUITE,
PROBE_L, PROBE_M, PROBE_LOAD, LITERATURE and EOM. TPC also
generates from the table a JSON Schema 2020-12 document,
schema_json, published beside it, non-normative: it carries the
keys, the required fields per CLASS, the types and the
enumerations, and names the TPC function that checks each grammar
the table leaves to TPC, each enumeration every value the table
allows the field at landing, GRADE's the class's landing grade
alone, an inherited record landing at it too (3.4.2); no rule
reads it and no check validates against it (7.1.61). [D192.2]
[S100] [D215.2]