4.6 The strike shape and the known limit (TPS 0.5.0)

Instruction artifact, machine-optimized text: TPS, section 4.6 The strike shape and the known limit. 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 4.6  THE STRIKE SHAPE AND THE KNOWN LIMIT
purpose: the withdrawal record's five fields; no container-level
         invalidation; a(r) gameable, atomicity INSPECTION
governs: 4.6 | version: 0.5.0 (proposed) | class: instruction artifact
audience: operator, agent

4.6.1  STRIKE SHAPE. A strike is a withdrawal record: entry-level,
       forward-only, carrying what it withdrew, what withdrew it, what
       supersedes it, what still stands, and the withdrawing version.
       Container-level invalidation is not in the shape. Its fields are
       the WITHDRAWAL record's (3.3.3): what still stands is
       still_stands, the withdrawing version tps_version with d_tms.
       [D194.1] [I-078]
4.6.2  A STRIKE is a withdrawal record in the strike shape, issued under
       SR1-SR9 (see 1.1, 3.3.3). A strike writes STATUS REFUTED into the
       struck record and its WITHDRAWAL sets the grade, on the pattern
       of the hold (3.2.10, 3.3.14); a HELD record is not struck but
       held, its prior status, the status word, kept, and a strike on an
       audit outcome is a decision item (4.1.5). [I-036] [D111.1]
       [D193.2] [D194.1]
4.6.3  NAMED COMPLETENESS DEFECTS, replacing the single known-limit
       line of the first revision (D41.2):
         (1) bundling. Atomicity remains a judgment, now made once per
             assumption at the allocation of its ASSUMPTION RECORD
             (see 4.2, row 23).
         (2) s(r) moves with record boundaries: a(r) runs over the
             closure while s(r) counts r's own derivation only.
4.6.4  OPEN AND STATED (D41.2). Under-declaration, an assumption or a
       citation left out, is an SR2 validity failure and is caught
       exactly as well as derivations are checked. Step granularity
       rests on the UWC's STEP CONVENTION; TPX counts declared steps.
4.6.5  The seven adversarial cases run in the synthetic suite as a
       REPORT-ONLY corpus: bundling many assumptions into one; hiding
       assumptions transitively; importing assumptions through cited
       records; choosing a favorable derivation decomposition; creating
       artificial short derivations; splitting one assumption into
       many; strategically choosing record boundaries. No probe is
       added to the certification suite and N is unchanged (see 5.14,
       7.2). [D41.2]