5.6 Certificate, declarations and the build chain (TPS 0.5.0)
Instruction artifact, machine-optimized text: TPS, section 5.6 Certificate, declarations and the build chain. 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, declared final as TPS 0.5.0 by H-DECL on 2026-10-03 (naming TPS_0.5.0.txt by its file digest and its D(TPS)); 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, verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.
TPS 5.6 CERTIFICATE, DECLARATIONS AND THE BUILD CHAIN
purpose: the candidate certificate and its landing; the two chain pages
and their contents; hashes; retirement declared on the
DECLARATIONS page; the build lines; the chain lines of
D119-D128 and of PRB's releases; the STRUCTURE LINE declared;
the MODULE DECLARATIONS
governs: 5.6 | version: 0.5.0 (proposed) | class: instruction artifact
audience: operator
5.6.1 The chain is two pages: the DECLARATIONS page, protected to the
declaring authority, append-only, carrying the genesis line,
certificates, UWC STATE (CERTIFIED, RETIRED, RESTORE, FORK, and
the ACCESS POLICY and AUDIT TRIGGER), the H-OWN binding,
admissions (each naming the sponsor and the fingerprint TPX
derived; the admission that seeds the reference account and the
user Prime, CR11, CR12), overrides, pads, removals and
closeouts; and the BUILD CHAIN page, appended by TPX, one line
per build naming the declaration line it verified against. Both
carry content digests, never revision IDs, so they survive
export. [I-063] [I-037] [D52] [D119.1] [D123.1] [D127.1]
5.6.2 Chain link hash SHA-256; page hash may be MediaWiki's SHA-1. The
manifest never contains its own digest. The genesis line is the
version and D(TPS) of the declared TPS (CR9, 5.11.2). [I-063]
[F2] [I-117] [D203.1]
5.6.3 Digests are computed at CAC by TPX, written into the CAC
certificate that assigns the UUID, and appended as a BUILD CHAIN
line (see 2.5.1). [I-062]
5.6.4 Certificate flow: TPX computes the digests and writes a candidate
certificate to staging; the named human declares certification by
landing it on the DECLARATIONS page. Neither side can do the
other's part. [I-065]
OWED: the specification of the candidate certificate's
computation, executed by TPX; kind: absence; C-09.
5.6.5 A retired container stays in the index in state RETIRED, pages
protected read-only, the retirement declared on the DECLARATIONS
page, back-pointers resolve directly (see 5.11.6). [B-10] [I-121]
5.6.6 No agent writes on any page carrying a declaration (see 5.13).
[I-106]
5.6.7 GENESIS TIMING. The DECLARATIONS page does not exist before its
genesis line (5.6.2, 5.11.2). It is created by the declaring
authority's first declaration, which declares TPS, at TPX's first
landing: TPX computes the genesis line's D(TPS) (CR9), since TPX
is the sole implementation of every digest (5.1, 5.6.3), and no
hand-transcribed digest ever enters the chain. Before that
landing there is no chain, and a bootstrap import creates no
chain page (5.11.2). A declaration made before that landing that
a version of this artifact is final is a version declaration,
recorded in the foundations record; it creates no chain page and
moves no digest. [I-159] [D83.1] [D203.1]
5.6.8 BUILD LINES (D112.1, D125.2). One BUILD CHAIN line per deployed
TPX build carries the Git commit fingerprint and the SHA-256 of
the deployed tree, and one per deployed W2 build its build
digest (5.3.23, 5.3.29); a deployment and a rollback are each
chain-recorded. A reader checks the method against the published
pseudocode and the deployment against the chain.
5.6.9 CHAIN LINES ADDED (D119.1-D128.2a): the community ledger's
content hash at every landing that touches it (5.9.13); the KEY
ID and every KEY ROTATION (5.3.27); every override, pad,
cancellation and expiry, on the DECLARATIONS page, its line
carrying account by fingerprint, value, nonce, server time and
reason, its digest the chain link, a duplicate nonce refused,
effective after OVERRIDE DELAY unless cancelled by a second
declaration, published on both alert channels the moment it
lands (CR11); every tuning-option change, naming the option, the
old and new value and the account (5.3.30); every dossier
rewrite's content hash (5.3.27). [D119.1] [D122.1] [D123.1]
[D127.1]
5.6.10 CHAINS OF VOLUMES (D141.1). Each of the two chains is kept as a CHAIN
HEAD over APPEND VOLUMES of VOLUME SIZE lines. The existing titles
become the heads; each head names its chain's open APPEND VOLUME and is
rewritten by TPX only when a volume opens. Each volume's first line
carries the previous volume's last digest and links to it, so each
chain stays one linear hash chain, verified from genesis through the
volumes, never through the head. A head carries no declaration and is
not append-only; the append-only protection is on the volumes (5.13.2).
The genesis line is the first line of DECLARATIONS Volume 1; the TPS
declaration creates the head and Volume 1 together, neither existing
before it (5.6.7). "The chain is two pages" (5.6.1) and "one global
DECLARATIONS page; one global BUILD CHAIN page" (5.11.1) read as one
chain each, carried through its volumes. [D141.1]
5.6.11 THE DECLARATION FORM (D141.1). H-DECL makes every declaration on
TPX's declaration form: the revision is H-DECL's, and TPX
supplies in the same request the line's digest, its volume, the
carried link and the head, so no person transcribes a digest
(2.5). The form stays open during a digest-gate or integrity
halt, since RESTORE and FORK are what end one. If TPX cannot run
at all, H-DECL appends a HAND LINE by the platform's own edit,
carrying no digest; TPX supplies that line's digest in the next
line it writes. At a declaration of a TPS version the form
computes that version's D(TPS) and D(IS) and fixes them on the
line (CR9). [D141.1] [D203.1]
5.6.12 DECLARATIONS OUTSIDE D(IS) (D142.1, D143.1, D147.1, D148.1, D150.1).
The CLUSTER DECLARATIONS (the SOURCE DECLARATION; the CORE SET with
SPACING FLOOR, SE MAX and the SE DEFINITION; the EXCLUSION LIST), the
FALCON KIND DECLARATIONS with their CONFIDENTIAL flag, and the FALCON
SOURCE LIST are H-DECL's declarations on the DECLARATIONS page, outside
D(IS), so a change lapses no certificate; before TPX's first landing
they are recorded in the foundations record and carried to the page at
its creation. The EXCLUSION LIST is named on the DECLARATIONS page
alone; no page of this artifact names an excluded vendor or model
(5.19.5). [D142.1] [D143.1] [D147.1] [D148.1] [D150.1]
5.6.13 CHAIN LINES ADDED (D133.1-D166.1): GOVERNOR OFF and AGENT STOP, each
set and lifted (5.3.38); every MODEL MAP change (5.14.4); the SHA-256
of each top performer download (5.19.5); the FALCON LOG's content hash
at every landing that touches it (5.20.19); every SPONSOR GRADUATION
grant, by TPX's UserGroupsChanged handler (5.14.10). [D133.1] [D136.1]
[D142.1] [D148.1] [D156.1] [D163.1]
5.6.14 DECLARATIONS ADDED (D170.1, D172.1). UWC STATE on the DECLARATIONS
page carries the BIBLIOGRAPHY SETTING (OFF, ON or CLOSED) with the
certificate, and each later declaration OFF to ON or ON to CLOSED
(5.21.1). The REGISTRY DECLARATIONS (5.21.14) and the FK-20 FALCON
KIND DECLARATION (5.21.17) are H-DECL's declarations on the
DECLARATIONS page, outside D(IS), on the pattern of 5.6.12, so a
change lapses no certificate; before TPX's first landing they are
recorded in the foundations record and carried to the page at its
creation. [D170.1] [D172.1]
5.6.15 CHAIN LINES ADDED (D182.1): one BUILD CHAIN line per PRB release,
carrying its version, the Git commit fingerprint, the SHA-256 of
the release artifact and the genesis digest it pins (5.4.21); the
tuning options of 7.2.29 are chained on every change, as every
tuning option is (5.6.9). [D182.1]
5.6.16 MODULE DECLARATIONS (D178.1 (b), (g)). The MODULE DECLARATIONS
are H-DECL's declarations on the DECLARATIONS page, outside
D(IS), on the pattern of 5.6.12 and 5.6.14, so none lapses a
certificate or moves a digest: MODULE ADD and MODULE VERSION,
each naming ID, VERSION, the text's digest and the date; MODULE
RETIRE and MODULE REINSTATE, each naming ID, VERSION and the
date; MODULE WITHDRAW, naming ID, VERSION, the reason and the
date, and optionally the version it offers again. Each is made on
TPX's declaration form, TPX computing the digest (5.6.11) and
refusing an act the CATALOGUE STATE refuses (5.22.10). The order
of the lines is the status: TPX computes every version's status
from them in chain order and stores none as an editable field. A
certificate landed on the page carries its MODULES USED (5.22.8),
declared with it and never rewritten, and the answers H-DECL gave
at the gate (5.22.6, 5.22.14). Before TPX's first landing each
act is H-DECL's own, recorded in the foundations record and
carried to the page at its creation (5.22.18). [D178.1]
5.6.17 DECLARATIONS ADDED (D176.1). A certificate landed on the
DECLARATIONS page carries its STRUCTURE LINE (5.5.3), declared
with it and never rewritten. While a UWC's EOM-0 is OPEN,
H-DECL may declare, as a line of UWC STATE, that the gap of one
UNDER unknown stands, naming the UWC and the unknown; the line
settles that unknown (3.3.16). [D176.1]