3.3 Record classes and schemas (TPS 0.3.0)
Instruction artifact, machine-optimized text: TPS, section 3.3 Record classes and schemas. 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. This page is revision 6 of the tree, proposed as version 0.3.0 until H-DECL declares it; revision 5, proposed as 0.2.0, stays undeclared and is carried whole. The text below is this section of the TPS artifact at 0.3.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.3 RECORD CLASSES AND SCHEMAS
purpose: the master record and its two departures; entry-status,
corroboration, withdrawal, named-gap and verification record
forms, owed; the GRADE treatment of the master record; the
HOLD and RELEASE record forms, with the bibliography list; the
status value HELD; a ledger MATCH as a reproduction; the
objective EOM-0
governs: 3.3 | version: 0.3.0 (proposed) | class: instruction artifact
audience: operator, agent
3.3.1 MASTER RECORD. The register's representation of the TFK. It
cannot be amended (a change is a new container), and it is
allocated by CAC at certification, not by the container's mark.
Every other record is checked at CAC against the register and
against the master record. [I-032]
OWED: the master record schema; kind: absence; C-13.
OWED: the "not graded" treatment of the master record's GRADE
field; kind: absence; C-14.
3.3.2 Entry-status record: the register record that carries an entry's
mutable fields STATE, SCRUTINY, RIDER, NOTE, CHECKS OWED, RECORDS
(see 2.1.3). [B-05]
OWED: the entry-status record schema; kind: absence; C-13.
3.3.3 Withdrawal record: a strike is a withdrawal record in the strike
shape (see 4.6). [I-078]
OWED: the withdrawal record form imported from the guide; kind:
absence; C-13.
3.3.4 Corroboration record: a refused block whose result matches the
landed one lands as a corroboration record naming the record it
reproduces, carrying the reproducing account, inheriting the
landed tag, and stating the reported difference; the block
closes as CORROBORATED (see 5.9). A REPRODUCTION block's match
lands the same way whether the lead commissioned it or TPX did
as a PARROT (5.9.11, 5.17.2); a within-UWC parrot's match is a
corroboration record in the source register, and a cross-UWC
parrot's pass lands on the COMMUNITY LEDGER and nowhere else
(5.9.12). A mismatch is a NON-CORROBORATION, logged, never a
corroboration record (5.9.7). [B-11] [D118.1] [D119.1]
OWED: the corroboration record form; kind: absence; C-13.
3.3.5 Named-gap record: an M contradiction of an L record with a(r) > 0
is recorded against r's ASSUMPTIONS as a named gap (SR7); the
ASSUMPTIONS of a struck record outside the closer record's closure
are recorded as the locus (SR5); an untied DOF is a named gap
(see 2.3.6, 4.4). [I-074] [I-072] [I-124]
OWED: the named-gap record form; kind: absence; C-15.
AMENDED (D176.1). An unknown DOF that the structure check finds
determined by no form (UNDER) is a named gap as well, named on
the STRUCTURE LINE with its question; under STRUCTURE_CHECK ON
it opens EOM-0 (2.2.20, 3.3.16).
OWED: the named-gap record form carries an UNDER gap and its
settlement, the settling records or H-DECL's standing-gap line;
kind: absence; C-15.
3.3.6 Verification record: veracity lives outside the run: derivation
under benchmark quarantine, then post-termination comparison
against external sources, landing as a regime-M verification
record whose external value is a benchmark, never an output. A
comparison reports the difference, never the agreement (see 7.1).
[I-125]
OWED: the verification record class for external verification
results; kind: absence; C-07.
3.3.7 ASSUMPTION RECORD. One declared assumption, one record.
Named departures from the record form: no FINDING, no REGIME.
Its identifier comes from the UWC's prefix as any record's does.
Atomicity and duplication are inspected once, at the assumption
record's allocation (see 4.2, row 23). [D41.2]
OWED: the assumption record schema; kind: absence; C-13.
3.3.8 The corroboration record gains INDEPENDENCE, filled by TPX from
facts it holds: account; model snapshot and vendor;
implementation name and digest; block origin, one of SAME BLOCK
or REPRODUCTION BLOCK; NOT SERVED BEFORE, that TPX did not serve
the target record to this account through the buffer path before
the block, consumed by source selection and displayed, by no
ranking rule (5.17.4); SAME-SPONSOR, that the reproducing account
and the author's account have one sponsor (5.14 CR12), a match
so marked weighing zero for the sponsor's own evidence under
every setting and for the agents unless CROSS-CORROBORATION
allows it. MECHANICAL. A community-ledger MATCH carries the same
vector (3.3.15). [D42.1] [D44.1] [D118.1] [D127.1] [D128.2a]
3.3.9 Context, sources, environment and seed MAY be attached to a
corroboration, marked SELF-REPORTED. No rule consumes them.
[D42.1]
3.3.10 A corroboration whose model snapshot equals the original's is
marked SAME-MODEL and is excluded from every corroboration count
TPX displays and from CR7's redundancy claim (see 5.14).
[D42.1]
3.3.11 HOLD RECORD (D111.1). Written by TPX after a failed canary, from
its reserved range (3.1.11), as the audit trail of a hold. Form:
[hold_id, HOLD, canary_id, account, snapshot, failing_block,
anchor_kind, anchor_block, lookback_passes, held_blocks, seeds,
held, biblio, digest]
anchor_kind is PASS or ADMISSION (5.14 CR6); held_blocks the
blocks from the anchor to the failing block inclusive, in history
order; seeds the records held directly; held the list
[[id, prior_status], ...] sorted by identifier in code point
order; biblio the list [[bib_id, check], ...] of the BIBLIOGRAPHY
ENTRIES the account proposed or landed in the held blocks whose
re-run CHECK value is not CONFIRMED, sorted, empty when the UWC
keeps no bibliography or nothing is listed (5.21.13; D171.1). The
digest is digest_fields (2.5.10) over the tagged, counted, flat
field list ["TPC-HOLD", "2", canary_id, account, snapshot,
failing_block, anchor_kind, anchor_block, lookback_passes,
n_blocks, block..., n_seeds, seed..., n_held, id, status, ...,
n_biblio, bib_id, check, ...], seeds, held and biblio sorted
first, so one hold digests alike whatever order its lists arrive
in; hold_id is the address and is outside the digest. Form "2"
replaced form "1" when the bibliography list was added; a HOLD
without the list is refused. TPX refuses to write an empty hold: a
failing block that landed nothing, supplied no corroboration and
vetted no RETURN holds nothing, and the failure's own record is
the canary outcome (5.17.15, 5.18). A record already HELD or
REFUTED inside the closure is listed with that status as its
prior status; at release it is restored no further than a HOLD
still in force allows, a check TPX makes over every HOLD not yet
fully released. [D111.1] [D171.1]
3.3.12 RELEASE RECORD (D111.1). Written by TPX after an eligible reproduction
matches a held record. Form:
[release_id, RELEASE, hold_id, hold_digest, kind,
reproduction_id, account, snapshot, restored, still_held,
biblio, digest]
kind is REPRODUCTION (a REPRODUCTION block, 5.9.9) or LEDGER_MATCH
(3.3.15); restored the list [[id, restored_status], ...] and still_held
the identifiers this hold still holds, both sorted; biblio the HOLD's
bibliography list carried unchanged, a release moving no entry. The
digest is digest_fields over ["TPC-RELEASE", "1", hold_id, hold_digest,
kind, reproduction_id, account, snapshot, n_restored, id, status, ...,
n_still, id, ..., n_biblio, bib_id, check, ...]. TPX first recomputes
the HOLD's digest, the bibliography list inside it, and refuses a
mismatch; then checks eligibility: the reproducing account is not the
held account; the reproduction is not SAME-MODEL, by the attested flag
or by a reproducing snapshot equal to the held snapshot, either
refusing; its origin is REPRODUCTION BLOCK (a SAME BLOCK corroboration
is not a reproduction). Then the matched seeds leave the seed set, the
closure is recomputed over the remaining seeds, and every held record
no longer reached is released with its prior status; a matched record
still reached by a remaining seed stays held, since a standing record
may not cite a held one; a release that would release nothing is
refused. A mismatch, or no eligible reproducer, opens an audit block
whose decision item strikes, restores or restricts DOMAIN (4.1.6).
[D111.1] [D171.1]
3.3.13 HELD PROPAGATION (D111.1). The held set is the closure over
reverse edges from the seeds: a record is held when any
identifier in its citations or its ASSUMPTIONS is held,
transitively, a visited set stopping a cycle; an identifier that
is not a record of the register (the TFK's) is ignored. The
seeds, each bounded by the held blocks, are: (S1) a record the
account authored in a held block; (S2) a corroboration the
account supplied in a held block; (S3) a record the account
vetted as AI-LEAD, in the lead's own block at incorporation,
defaulting to the record's own block when no vetting block is
recorded, that block being held. The account's older work is
reviewed, not held (5.14 CR6). The functions hold_scope,
held_closure, hold_record and release_record are TPC functions
with vectors in both residences (5.1.5). [D111.1]
3.3.14 WITHDRAWAL SETS STATUS (D111.1). A strike is likewise a
separate withdrawal record (3.3.3, 4.6), so every withdrawal also
sets the struck record's own status, on the pattern of the hold:
the status on the record itself, the separate record as the
audit trail.
OWED: the status value a strike sets, and the register's grade
set, wait on the record field schema; kind: absence; C-16.
3.3.15 A COMMUNITY-LEDGER MATCH AS A REPRODUCTION (D119.1). A MATCH on
the community ledger (5.9.12) whose INDEPENDENCE passes the
eligibility check of 3.3.12 is a reproduction for the purpose of
RELEASE, kind LEDGER_MATCH; TPX writes the RELEASE on it under
COMMUNITY PARROTS ACCEPT (5.16.11), and writes the corroboration
record from its reserved range (3.1.11). The trust-tier gate on a
ledger MATCH (5.14 CR11: only a TRUST TIER member's match
releases) is one more refusal in the same check, an obligation
for when the score is enforced, not a completeness defect.
[D111.1] [D119.1] [D122.1]
3.3.16 OBJECTIVE EOM-0 (D176.1). A UWC declared with STRUCTURE_CHECK
ON whose STRUCTURE LINE names an UNDER finding opens with the
objective EOM-0, which TPX sets OPEN on the landing that
instantiates the UWC (5.5.4): its first register work settles,
for each UNDER unknown, the law that determines it. While EOM-0
is OPEN general pushes wait: TPX lands a PUSH only from a work
block of KIND EOM-0 or REPRODUCTION (5.8.3) and refuses any
other with the reason EOM-0 OPEN. TPX's own writes (HOLD,
RELEASE, a ledger corroboration) are not pushes and do not
wait. An UNDER unknown is settled by a standing L record
deriving its equation from the TFK in a declared form, or by a
standing ASSUMPTION record supplying it, priced in a(r), either
carrying on its declared form ROLE EOM(q) or another ROLE that
enters the matching; or by H-DECL's declaration that its gap
stands, a line of UWC STATE naming the UWC and the unknown
(5.6.17). An initial value's ASSUMPTION record declares no ROLE
and settles nothing (3.2.15). TPX checks the settlement inside
the PUSH with the later test's function over the TFK and the
standing records whose declared form carries a ROLE (5.3.47),
and closes EOM-0 when every UNDER unknown is determined or
declared standing. An OVER-EOM, OVER, CLOSED or ROLE MISMATCH
finding never opens EOM-0: the register cannot repair the TFK,
whose repair is COPY-FORWARD (2.1.2). A CLOSED EOM-0 does not
reopen: a later test that finds an UNDER unknown again is
information, on which H-DECL may open an audit block (5.3.47).
Under STRUCTURE_CHECK OFF no EOM-0 opens.
Until the record field schema gives records a declared form,
the check reads the TFK alone and the register part is the
lead's INSPECTION: the lead's PUSH names, in its EOM-0
SETTLEMENT field, the record that settles each UNDER unknown;
TPX records the naming on the control panel with the lead's
account as an INSPECTION and closes EOM-0 on it, ratchet debt
(4.2.14).
OWED: a declared form on a register record, its ROLE in the
vocabulary of 2.2.6, and the EOM-0 SETTLEMENT field's shape;
kind: absence; C-16.
[D176.1]