Jump to content

The Principia Machina/TPS/5.10 The badge and staleness: Difference between revisions

From The Invariance Itself
Post-TPC-PY page batch B3 (S154, S159): TPS revision 8 (proposed TPS 0.5.0)
m 1 revision imported
(No difference)

Revision as of 13:34, 30 September 2026

Instruction artifact, machine-optimized text: TPS, section 5.10 The badge and staleness. 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 5.10  THE BADGE AND STALENESS
purpose: the badge fields written last; release after push; CURRENT,
         STALE, HOLDER SILENT with reader conditions; the three citation
         levels defined generically
governs: 5.10 | version: 0.5.0 (proposed) | class: instruction artifact
audience: operator, agent

5.10.1 BADGE on the wiki manifest, written LAST by TPX at the end of
       every landing as the commit marker: HOLDER, GRANT, EXPIRY, LAST
       PUSH, LAST RELEASE, CHAIN LINE, MANIFEST REVISION, D(IS); all
       times server time. A release is valid only after a push. [I-084]
5.10.2 States computed by the reader: CURRENT (no holder; LAST PUSH >=
       LAST RELEASE; page hashes match the manifest) - any reader,
       citations VERIFIED. STALE (holder within expiry, or hashes
       mismatch) - no use except an audit block for disposition; auditor
       citations VERIFY. HOLDER SILENT (holder past expiry, no release)
       - no use except an audit block; auditor citations VERIFY-HIGH,
       cause "holder silent past expiry"; the queue head may acquire; a
       late push is refused by fencing (D19). [I-084] [I-039]
5.10.3 Every wiki reader, other-thread escalation included, computes the
       state before use; waiting is a strategy only in STALE. [I-085]
5.10.4 Citation levels. VERIFIED: confirmed against a CURRENT wiki copy.
       VERIFY: read from a copy not known CURRENT; best-available
       evidence, unconfirmed. VERIFY-HIGH: known to be at risk, cause
       named. An unlabeled citation is VERIFY. [C-26] [I-007]
5.10.5 THE BADGE'S EXPIRY (D141.1). The badge's EXPIRY is written at every
       landing and also at acquisition, at release and at each EXPIRY STEP
       (5.7.9), and carries exactly the expiry TPX enforces; the badge stays
       written last at a landing, on the MANIFEST TREE's root (5.11.11).
       [D141.1]