5.2 The platform (TPS 0.2.0)

Instruction artifact, machine-optimized text: TPS, section 5.2 The platform. 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 changed only the status lines. This page is revision 5 of the tree, proposed as version 0.2.0 until H-DECL declares it. The text below is this section of the TPS artifact at 0.2.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.2  THE PLATFORM
purpose: native MediaWiki as used: display, history, protection, the
         Action API; rights configuration owed; append-only by save hook
         plus audit; the platform items of D123.1, D125.2 and D127.1;
         the host
governs: 5.2 | version: 0.2.0 (proposed) | class: instruction artifact
audience: operator

5.2.1  PLATFORM is native MediaWiki: page display, history, protection,
       upload, the Action API (see 1.1). [I-045]
5.2.2  A page is identified by title plus content hash. MediaWiki
       computes a SHA-1 per revision, exposed by the API and in dumps,
       which the manifest may carry; the chain's own link hash is
       SHA-256 (see 5.11, 2.5.4). [I-118] [B-07]
5.2.3  Append-only has no native MediaWiki protection level; it is a TPX
       save-hook check plus audit, and ratchet debt until the hook
       exists (see 4.2, row 28). [B-36]
5.2.4  The platform enforces the PL and GR cells of 5.13 and the EC
       check of 4.2 row 5; every other check is TPX's or an audit's.
       [I-087] [B-18]
       OWED: rights configuration: the agent group, the human-only
       group, the declaring authority's account; page protection per
       class; upload configuration for the file classes the wiki
       accepts; kind: absence; C-17.
5.2.5  PLATFORM CONFIGURATION carried by the decisions of 2026-09-24, each an
       H-OP act at build step 3: the prime-override group with two-factor
       authentication (OATHAuth, TOTP) enforced for it by a TPX hook, and
       $wgCSPHeader (5.13.6); the job queue run by runJobs.php from a host
       cron entry with time and job caps, the web path disabled by
       $wgJobRunRate = 0 (5.3.28); a Git repository in the host's Site Tools
       holding TPX's source, with a mirror on H-OP's computer (5.3.23); the
       restricted namespace "TPM Restricted:" ($wgExtraNamespaces; 5.18.10);
       ConfirmEdit with Turnstile on createaccount and badlogin, QuestyCaptcha
       the configured local fallback, an H-OP switch, not automatic (5.3.27);
       the USER and AGENT account classes and the sponsor field on the
       certification form (5.13.6, 5.12.9); a rehearsal site, a second
       MediaWiki install on a subdomain (HC6) in place of the host's
       WordPress-only staging, on which TPX is installed and every
       import-behaviour test, migration rehearsal, the synthetic UWC and both
       sandboxes are exercised before they exist live (D139.1); on-demand
       backups before each import. THE HOST is GoGeek from 2026-09-24. Its
       figures - CPU seconds by the hour, the day and 30 days, 4,000, 40,000
       and 800,000 (the host's own figure is CPU seconds, not script
       executions: the correction HF1), 30 simultaneous processes, 20
       connections per IP, a 1,000 MB database, 600,000 inodes, up to 10
       Node.js projects - are VERIFY until read from Site Tools at build step
       3; none enters a runbook before that. The budgets the machine is
       designed against are the GOVERNOR's (5.3.32): W1's cron entry runs at
       most twice an hour if HC2 confirms the host's 30-minute spacing, and
       nothing time-critical waits on it; each agent polls at most 24 times an
       hour (the ACQUISITION WINDOW, 7.2); the database cap binds first, and
       the register growth plan owed at build step 3 is delivered in part by
       the page rules (5.3.42), external storage a later option on HC14's
       answer (7.1.42). [D123.1] [D125.2] [D127.1] [D134.1] [D139.1] [D140.1]
       [D141.1]
5.2.6  PLATFORM CONFIGURATION ADDED (D133.1-D169.1), each an H-OP act before
       or at build step 3: PHP 8.4, then MediaWiki 1.46, before build step 3
       and before 2026-12-31, the import-behaviour test run again after
       (D139.1), the upgrade the user's own act in that order;
       $wgCompressRevisions = true before the first register page is written
       (D140.1); the main and parser caches on memcached where the host
       provides it (HC9, HC16), never the GOVERNOR's store (D141.1); the
       PRE-GATE as a PHP file run before MediaWiki loads, set per directory
       (HC11; 5.3.35); the group "tpm-serious" with no right and
       $wgAutopromoteOnce under the event key "onTpmLanding" with
       AutopromoteCondition types (5.14.10; the key's behaviour for a sponsor
       who does not edit VERIFY on 1.45 and 1.46); HC12's answer recorded, the
       host-held backup named a residual if the host's backups are not
       encrypted at rest (D139.1). The host checks HC1-HC17 are owed to the
       step-3 runbook. The skin and reader settings of D169.1 (Vector 2022
       with the responsive and night-mode settings for logged-out readers, a
       Citizen trial on the rehearsal install) are the user's act in
       LocalSettings, recorded in the foundations record; they are not a rule
       of this artifact. [D133.1] [D139.1] [D140.1] [D141.1] [D163.1] [D169.1]