7.2 Declared parameters (TPS 0.1.0)

Instruction artifact, machine-optimized text: TPS 0.1.0, section 7.2 Declared parameters. 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 7.2  DECLARED PARAMETERS
purpose: ACQUISITION WINDOW, N, CANARY RATE; where a change is made
governs: 7.2 | version: 0.1.0 (proposed) | class: instruction artifact
audience: operator, agent

7.2.1  Declared by the declaring authority on 2026-09-13. [I-135]
7.2.2  ACQUISITION WINDOW  5 minutes, server time (D18). Consequence: the
       agents' polling interval is at most 2.5 minutes, since the window
       is not less than twice it (see 5.8.5). [I-132]
7.2.3  N                   One operation per fail type in the
       certification suite in force (CR4): N equals the number of probe
       types. The suite as recorded carries six probe types, so N = 6
       until the suite changes (see 5.14). [I-133]
7.2.4  CANARY RATE         One probe per five work blocks (CR6) (see
       5.14). [I-134]
7.2.5  TMS parameters (STEP CONVENTION, k, N_x, local yardsticks) are per
       container and are not declared here (see 2.4.5). [I-080]
7.2.6  These values live in TPS. Changing any value is a revision of TPS;
       an implementation follows the published value. [I-135] [AUTHORED]
       NOTE: the wording of the implementation's own parameter line is
       an O8 item (tps_inventory G-06).
7.2.7  SEQUENTIAL TEST. The fleet-level test of 5.18.2 and 5.18.9 runs
       at alpha = 0.10 and beta = 0.01, testing between H0 p = 0.99
       and H1 p = 0.95 over the removal rate. Fleet level only; no
       account-level test exists under binary scoring (5.18.9).
       Declared 2026-09-21. Changing it is a revision of TPS.
       [I-144] [I-146] [D84.1]
7.2.8  THE PAGE TREE IS VERSION-AGNOSTIC. No version number appears in
       the title of a page of this artifact. A revision edits the
       existing tree in place; it does not spawn a new one. The
       version a page carries is stated in its display title, its
       header string and in 0.1, never in its title. Those live in the
       page text, so an old revision displays the version it was.
       [I-155] [D54]
7.2.9  GROUND FOR 7.2.8. With a version-free title a page's revision
       history IS its version history, which is what the platform
       provides and what 1.3 declares the wiki to be for. A versioned
       title builds a second and worse version-management system
       beside the platform's own and fragments each version's history
       into its own tree. A rename costs no history: the platform
       moves a page's whole history to the new title and leaves a
       redirect. What loses live history is a delete followed by a
       reimport, which is therefore not how this artifact's tree is
       ever restructured. [I-156] [D55]
7.2.10 An earlier version of a page is read from that page's history.
       There is no separate tree to browse, and the contents page and
       the hub say so (see 5.15). [I-156] [D55]
7.2.11 THETA INTERVAL. theta is drawn per epoch from Uniform[2.0, 4.0],
       endpoints strictly interior (5.17.7, 5.17.8). The lower bound is
       refitted from the distance distribution of real work once three
       or more UWCs carry records; the refit is a revision of TPS.
       [I-144] [D61.1]
7.2.12 ROTATION. An epoch ends with probability 0.10 per canary
       delivered, so its length is Geometric with mean 10 canaries. It
       counts canaries delivered, not wall-clock time (5.17.7).
       [I-144] [D62.1]
7.2.13 SCORECARD CADENCE. An exception check every week: the scorecard
       is sent when an exception is found, and a heartbeat otherwise. A
       full report every month regardless (5.18.5). [I-146] [D63.1]
7.2.14 RECIPIENTS. The failure alert goes to the declaring authority
       with the human operator copied; the periodic scorecard goes to
       the human operator with the declaring authority copied. Each
       role's account binding is published on the control panel
       (5.18.8). [I-146] [D64.1]
7.2.15 ALERT CHANNEL. The primary is SMTP carrying a pointer only. A
       secondary channel is required: content-free, out of band and not
       wiki-native. Its concrete choice is declared before TPX builds
       the alert path. A wiki-native notification is in-band and is
       disqualified (5.18.3). [I-146] [D65.1]
7.2.16 REVIEW POINT. When 200 canaries have been delivered fleet-wide,
       the theta interval, the rotation probability and the sequential
       test's hypotheses are revisited. [I-144] [D66.1]