3.2 Record fields and regime (TPS 0.1.0)

Instruction artifact, machine-optimized text: TPS 0.1.0, page 3.2 Record fields and regime. Part of TPS 0.1.0 and the TPM hub. Human-only edit (TPS 5.13). Version 0.1.0, proposed, revision 2; declaration pending. Governing section: this page, TPS 3.2. The text below is this page's unit of the TPS 0.1.0 artifact, verbatim; the whole artifact and its file digest are on The Principia Machina/TPS 0.1.0. Human readers: the contents page is the map.

TPS 3.2  RECORD FIELDS AND REGIME
purpose: the field schema ASSUMPTIONS, REGIME, DERIVATION, VALUE with u_c
         and Type B list, owed; regime L or M assigned at allocation
governs: 3.2 | version: 0.1.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.
       [B-14] [C-16]
       OWED: the record field schema, the field set with its types and
       constraints; kind: absence; C-16.
3.2.2  A record carries a FINDING, tested against the TFK by the strike
       rule (see 4.4), and a tag, inherited or assigned as 3.4 and 5.9
       state. [I-068] [B-04] [B-11]
3.2.3  DOMAIN is required on every promoting record (see 2.3.3). [I-030]
       OWED: the promotion mechanism, what a promoting record is and what
       promotion does to a TrM entry; kind: absence; C-31.
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 record states u_c with its Type B components enumerated
       (see 4.4, SR8). [I-075]
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 is refused on write (see 4.2, rows 19 and 22).
       [B-18]