5.10 The badge and staleness (TPS 0.1.0)

Instruction artifact, machine-optimized text: TPS 0.1.0, section 5.10 The badge and staleness. Part of TPS 0.1.0 and the TPM hub. Human-only edit (TPS 5.13). Version 0.1.0, proposed, revision 4; declaration pending. The text below is this section of the TPS 0.1.0 artifact, 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.1.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]