The Principia Machina/TPS/2.4 The Measure Set

Instruction artifact, machine-optimized text: TPS, section 2.4 The Measure Set. 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 changed only the status lines. This page is revision 5 of the tree, proposed as version 0.2.0 until H-DECL declares it. The text below is this section of the TPS artifact at 0.2.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 2.4  THE MEASURE SET
purpose: A1-A3; the TMS parameters STEP CONVENTION, S_MAX, k, N_x,
         PROMOTION_FLOOR, IC2_POLICY and local yardsticks, declared
         per container and tested at CAC; the TMS schema and the
         yardstick grammar
governs: 2.4 | version: 0.2.0 (proposed) | class: instruction artifact
audience: operator, agent

2.4.1  The TMS is the third zone of the TFK: the strike skeleton's
       declared parameters, the regime and contradiction tests, and any
       local yardsticks (see 1.1, 4.3). [I-022]
2.4.2  A TMS MAY carry additional entries for precision or limiting
       cases. [I-067]
2.4.3  Every TMS entry passes SR9 at CAC certification, before the
       container's first round of research (see 4.5). [I-067]
2.4.4  TMS entries are immutable per container. [I-067]
2.4.5  TMS PARAMETERS, per container, declared at instantiation and
       tested at CAC: STEP CONVENTION (SR4); S_MAX, the depth of kernel
       test T3 (2.2.3); k (SR3); N_x (SR6); PROMOTION_FLOOR, F2 where
       the UWC does not say otherwise (3.2.12); IC2_POLICY, GAP or
       REJECT, GAP when absent (2.3.6); any local yardsticks. [I-080]
       [D92.1] [D98.1]
2.4.6  Every TMS instantiates the skeleton's parameters and may not
       relax (i) or (ii) (see 4.3). [I-066]
2.4.7  THE TMS SCHEMA. A TMS is an object with three parts. PARAMETERS
       is required; CONSTANTS and YARDSTICKS may be absent, which means
       empty. PARAMETERS:
         STEP_CONVENTION  prose; not blank (SR4)
         K                decimal; a positive finite double (SR3)
         N_X              integer, 2 to 1,000,000 (SR6)
         S_MAX            integer, 1 to 1,000,000: the T3 depth
         IC2_POLICY       optional; GAP or REJECT; GAP when absent
         PROMOTION_FLOOR  optional; F1, F2 or F3; F2 when absent
       An absent IC2_POLICY serializes as GAP and an absent
       PROMOTION_FLOOR as F2, so declaring the default and saying
       nothing give one digest. K must be a positive finite double
       because SR3 computes with it: 1e-400 and 1e400 are refused rather
       than silently becoming 0 and infinity. CONSTANTS: entries {NAME,
       VALUE}, VALUE a decimal; these are the named immutable constants
       SR9 C5 requires, and a yardstick uses no literal number.
       YARDSTICKS: entries {NAME, KEY, LIMITING}; KEY a list of terms;
       LIMITING a list of {DOMAIN, KEY}, a limiting case that replaces
       the KEY inside its declared DOMAIN and only there (SR9 C2),
       DOMAINs within one yardstick distinct after NFC. [D92.1] [D98.1]
       [D100.1]
2.4.8  THE TERM GRAMMAR of a local yardstick, closed:
         term := SR1 | A | S | FIELD:<ident> | NEG:<term>
               | WSUM:<wt>(;<wt>)*
         wt   := <constant>*<atom>
         atom := A | S | FIELD:<ident>
       SR1 is 0 for a record passing SR1 and 1 for one failing it; A is
       a(r); S is s(r); FIELD names a numeric record field, resolved
       against the record field schema by lookup, never by reflection
       (C-16). NEG negates; NEG prefixes are counted, not parsed
       recursively, an even count cancelling, so no depth of nesting
       can exhaust a residence. WSUM is a weighted sum whose weights are
       TMS CONSTANTS by name, each atom appearing at most once. A KEY is
       compared lexicographically, lower is closer. No yardstick is
       code: TPX executes nothing a page carries. [D100.1]
2.4.9  KEY RULES, checked at zone entry: KEY is not empty and begins
       with SR1, and SR1 appears nowhere else, so SR9 C1 holds by
       construction; every term parses and every weight is a TMS
       constant (SR9 C5); STATIC C2 on a main KEY, the first term whose
       value moves with A must move up with it, since adding one
       assumption raises a(r) by one and leaves s(r) unchanged, a
       limiting KEY being exempt inside its declared DOMAIN as SR9 C2
       allows. Static C2 treats FIELD terms as independent of the
       assumption count; the yardstick evaluator's run on the synthetic
       suite is the second line (4.5.3). [D100.1]
2.4.10 Resolution is not declarable: a yardstick orders records, and
       the framework's SR5 and SR7 resolve contradictions, so SR9 C4
       holds by construction. C3 holds for SR1, A and S and waits on
       C-16 for FIELD terms. [D100.1]