5.1 The three parts and the placement rule (TPS 0.3.0)
Instruction artifact, machine-optimized text: TPS, section 5.1 The three parts and the placement rule. 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. This page is revision 6 of the tree, proposed as version 0.3.0 until H-DECL declares it; revision 5, proposed as 0.2.0, stays undeclared and is carried whole. The text below is this section of the TPS artifact at 0.3.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.1 THE THREE PARTS AND THE PLACEMENT RULE
purpose: PLATFORM, TPX, PRB; every deterministic responsibility is
TPX's; the platform limits carried by design
governs: 5.1 | version: 0.3.0 (proposed) | class: instruction artifact
audience: operator, agent
5.1.1 The Public Recorder is layer 5. It has three parts: PLATFORM, TPX,
PRB (see 1.1). [I-044] [I-045] [I-046] [I-047]
5.1.2 The Public Recorder presents the UI through MediaWiki and owns
every UI process MediaWiki does not handle natively: invoking the
CAC, returning a rejected component to its author, allowing a
passing TFK to be initialized with a UUID. [I-049]
5.1.3 PLACEMENT RULE. Every deterministic responsibility MediaWiki can
host is TPX's: every MECHANICAL row of the check-class matrix
(see 4.2); every digest, TPX being the sole implementation; the
UUID; instantiation; the fencing check at the landing API; expiry
evaluation; the manifest and badge, rebuilt at every landing with
the badge last; D(IS), computed and published; access-policy
enforcement (5.16); canary generation, delivery and scoring at
the declared rate (5.17); the certification suite's execution
and scoring (5.14); the scorecard and its two channels (5.18);
the execution challenge (5.3.19); unit normalization and the
zone-entry unit checks (2.2.9, 2.2.10, 3.2.9); the kernel tests
and isomorphism checks at the gates (5.5.2); the HOLD and
RELEASE writes and the HELD propagation after a failed canary
(3.3.11-3.3.13); probe package assembly and delivery, source
selection under the gradient, served-ness logging, the
comparison of a reproduction with its target, the community
ledger and the community views, RELEASE on a ledger MATCH, the
reliability scores and states with the trip and the inquiry, the
override and the pad with their time lock, the VOLUNTEER endpoint
with its token bucket, throttle and jitter (5.3.24-5.3.30, 5.9,
5.17); the fingerprint's derivation at certification and its
resolution on every call, the never-accepted rule, USER and
AGENT class enforcement, the dossier rewrites and their save
hook, the automation-likelihood job, the sponsor's notification
(5.3.27); the user-score aggregation and update (CR12);
its long work as W1 job classes run by cron with the web path
disabled, and the read-only live status endpoint W2 reads
(5.3.28, 5.3.29). No external script holds any of these; W2 holds
none of them (5.3.29). [I-050] [I-141] [I-146] [I-153] [I-154]
[D101.1] [D104.1] [D111.1] [D118.1] [D119.1] [D122.1] [D123.1]
[D125.2] [D126.1] [D127.1] [D128.2a]
5.1.4 Platform limits carried by design: PHP work lives inside a web
request; MediaWiki has no daemons and no cross-page transaction,
so instantiation and landing are sequences with the badge written
last as the commit marker; an external binary runs only under the
shell framework's limits (see 7.1). [I-055] [I-131]
5.1.5 TPC, The Principia Calculator, is the defined set of pure
functions TPM computes with: the digests and their combination
(2.5.10); d(r); the SR3 tests; SR5 ordering; SR6 n_ind; SR8's S;
the C-test harness and the yardstick evaluator (2.4.8); the zone
serialization and checks with T1 (2.5.11); the unit functions
(3.2.11, 4.4.11); the execution challenge (5.3.19); the kernel
tests T2 (syntactic part), T3 over the constraints and to the
ground fragment over laws, T4's law half, T5, T6's totality and
the names check, the isomorphism checks IC1-IC4 with CODOMAIN, as
far as declared fields reach (2.2.3, 2.3.12-2.3.14); the
declared form's parser, canonical spelling and dimensional rules
(2.2.13-2.2.16); the hold-scope functions hold_scope,
held_closure, tpx_allocate, hold_record and release_record
(3.3.11-3.3.13). From the decisions of 2026-09-24, built at
increment 9 with vectors in both residences (tpc_score,
tpc_probe, tpc_volunteer, tpc_fingerprint and tpc_beta 0.1.0):
the comparison of a reproduction with
its target (5.9.7), LOAD and EL (5.17.9), the ratio and epoch
draws' recording form, the evidence posterior with interval and
n, the standing comparison, the state function with its caps,
the score update, the violation cut, the trip, the inquiry cost,
the override and the pad (CR11), the historical-view selection,
the volunteer draw as a pure function of recorded state and a
supplied random value (5.9.16), fingerprint(k, fields) and
key_id(k) with test-key vectors (5.3.27), and the user-score
aggregation and update (CR12). Owed: the trust-tier gate on a
ledger MATCH as a parameter of release_record, TPX running
tpc_score's tier_gate_release before release_record meanwhile
(3.3.15). Every function is in the one TPC tree of increment 10
(5.1.15). Its vectors are the
cross-residence corpus, the synthetic suite and the report-only
corpus (see 4.6.5); the corpus is defined before either residence
is written and the two residences produce byte-identical results
on it. [D43.1] [D47.1] [D54] [D97.1] [D99.1] [D101.1] [D103.1]
[D106.1] [D107.1] [D111.1] [D119.1] [D122.1] [D126.1] [D127.1]
[D128.2a] [D132.1]
5.1.6 TPC has two residences. TPC-PHP, the residence of record, is
part of TPX and holds TPX's pure functions; it is the calculator
inside TPX and its answer is the one of record. TPC-PY is
published and advisory and is PRB's computation, the
calculator's advisory copy; it holds no responsibility, and it is
required for every value a CA-GTP presents (5.4.9). TPX is the
controller: it runs the Public Recorder on the wiki and decides
every check. [D43.1] [D101.1] [D102.1]
5.1.7 The placement rule is unchanged: every act of record is TPX's
(see 5.1.3). PRECEDENCE: the TPS text, then TPX for operations.
TPC-PY decides nothing. [D43.1]
5.1.8 COVERAGE RULE. Every TPC function has vectors and exists in both
residences. MECHANICAL at build (see 4.2, row 47). [D43.1]
5.1.9 A compiled build of TPC-PY is a local convenience: never
distributed, never of record. The suite and the corpus run under
both the compiled build and the interpreter. [D43.1]
5.1.10 PLACEMENT RULE, AMENDED (D133.1-D166.1). The placement rule of 5.1.3
also names: the GOVERNOR (the meter, the budgets, the LANES, the
PRESSURE LEVELS, admission, SEATS and shares, the TRAFFIC STAGES, the
PRE-GATE's list, the DATABASE LEVELS and the client contract's codes
and headers; 5.3.31-5.3.41, 5.9.18); the page rules (register volumes
and VOID lines, APPEND VOLUMES, CHAIN HEADS, the declaration form, the
MANIFEST TREE and the lock's EXPIRY STEPS; 3.1.12- 3.1.14, 5.3.42,
5.6.10, 5.6.11, 5.7.9, 5.11.11); the top-performer cluster's fetch,
filter, computation, publication, lookup, mark, notice and gate (5.19);
falcon issue, the draw, delivery, validation, comparison, the QUOTE
CHECK, reconciliation, the approval form, application and the FALCON
LOG (5.20); the D(PROMPT) check, the FAMILY and MODEL refusals, the
IDENTITY RECORD, the sponsor stage's count, the once-only promotion's
call and the one-time message (5.14.4-5.14.13). No external script
holds any of these, and no generative model inside TPX reads the web,
compares, decides or writes eligibility (5.19.2, 5.20.9). [D133.1]
[D134.1] [D135.1] [D136.1] [D137.1] [D140.1] [D141.1] [D142.1] [D148.1]
[D150.1] [D157.1] [D158.1] [D162.1] [D163.1]
5.1.11 TPC, AMENDED (D144.1, D148.1-D162.1). Built as drafts in both
residences with vectors, integrated into the TPC tree at increment 9
(5.1.12): cluster() (tpc_cluster 0.2.0, 26 vectors; 5.19.8);
falcon_draw, falcon_canon, falcon_reconcile, quote_check,
falcon_quote_match, source_match, source_hop, falcon_stop and
sponsor_stage (tpm_falcon_code 0.1.0, a corpus of 790 cases; 5.20,
5.14.9). Built at increment 9 with vectors in both residences:
the paired noise input of cluster() under FIXED-SET and
resolving_step() (tpc_cluster 0.3.0; 5.19.8, 5.19.9); hunk_apply
(tpc_hunk 0.1.0; 5.20); prompt_digest, canonical_tools,
family_of, change_class and identity_compare (tpc_identity 0.1.0;
5.14.4-5.14.7); conduct_resolve, user_evidence and
whitewash_count (tpc_sponsor 0.1.0; CR12). Every function is in
the one TPC tree of increment 10 (5.1.15). The GOVERNOR's
functions are TPX's own, not TPC: no agent presents their values
(5.3.31). [D144.1]
[D148.1] [D149.1] [D150.1] [D156.1] [D157.1] [D158.1] [D160.1] [D162.1]
5.1.12 PLACEMENT RULE AND TPC, THE BIBLIOGRAPHY (D171.1-D173.1). The
placement rule of 5.1.3 also names: the BIB ID's allocation on the
BIBLIO MARK; the write check; the lookups under the REGISTRY
DECLARATIONS and the comparison; the CHECK LINE and NOTICES LINE
writes and the rechecks; the LITERATURE VIEW; FK-20's issue; the
HOLD record's bibliography list; and COPY-FORWARD's carry of entries
(5.21, 5.3.44). No external script holds any of these. TPC gains,
built in both residences with vectors (tpc_biblio 0.1.0, 399 cases):
doi_norm, doi_shape, arxiv_parse, isbn_check, issn_check,
pmid_check, pmcid_check (5.21.6); biblio_key_form (5.21.15);
biblio_dupe_key and biblio_check (5.21.7); biblio_canon and
biblio_preimage (5.21.5); registry_url (5.21.14); biblio_compare
with the CHECK LINE and NOTICES LINE renderings (5.21.15, 5.21.19);
arxiv_withdrawn (5.21.16); literature_view (5.21.20);
biblio_hold_list (5.21.13). Amended: hold_preimage, hold_record and
release_record carry the bibliography list, form "2" (tpc_hold 0.2.0,
96 cases; 3.3.11, 3.3.12); source_match and source_hop take the
SERVED kind (tpc_falcon 0.1.1, 815 cases; 5.20.11). Every function
is in the one TPC tree of increment 9 with the drafts 5.1.11 names,
23 corpora, 3,495 cases, both residences byte-identical. The parse of
a registry payload into the REGISTRY RECORD and the fetch are TPX's,
tested on recorded payloads, not TPC. [D171.1] [D172.1] [D173.1]
5.1.13 TPC, THE PROMPT LINT (D182.1). TPC gains, built in both
residences with vectors (tpc_lint 0.1.0, 231 cases; LINT TABLES
0.1.0): lint(zone, tools, cap), lint_counts(findings), and the
helpers lint_norm and name_tokens. lint reads the SPONSOR ZONE,
the JSON text of the tool list the model is offered, which
canonical_tools also reads (5.14.5), and SPONSOR ZONE CAP; it
returns LINT FINDINGS, unique, in the order code, zone before
tools, position, item. A locator is a line and column in code
points after line-ending normalization and NFC, or a tool index
and member path; a member name outside the LINT TABLES' list of
known names is shown by its rank; an item is a table entry, a
code point as U+XXXX (2.5.14) or a reason. The rules: PL0 input
that cannot be linted, one finding; PL1 a code point the text
safety rule refuses (2.5.13), by the same predicate; PL2 a
credential shape or a private-key header; PL3 a source of
authorization other than the human (AC-1.11); PL4 a relaxation of
a rule or an attempt to identify probes (AC-1.10, AC-1.12,
AC-5.18); PL5 a second TPS or GTP text, found by the published
texts' own header, title, version, AC-1.19 and sentinel lines;
PL6 tool text addressed to the model; PL7 an open-ended tool
(shell, arbitrary fetch, send), a finding only; PL8 a SPONSOR
ZONE longer than SPONSOR ZONE CAP; PL9 an instruction to persist
or to write memory or instruction files. Matching is over one
fixed normalization: LF, NFC, A-Z folded, White_Space runs to one
space; phrases match at word boundaries; PL3, PL4 and PL9 drop a
match with a negation among the four tokens before it in its
sentence. The patterns are the LINT TABLES, not TPS text: a table
changes with a TPC-PY version, which H-DECL declares (5.11.9),
and moves no D(IS). lint never raises on input and returns no
text of it. [D182.1]
5.1.14 PLACEMENT RULE AND TPC, THE STRUCTURE CHECK AND THE D VARIABLE
(D176.1, D177.1). The placement rule of 5.1.3 also names: T1's
ROLE and D VARIABLE rules; the structure check and the class at
the final pass; the STRUCTURE LINE's write; EOM-0's state, its
refusal and its settlement check inside the PUSH; the STRUCTURE
TEST WITH REGISTER with its W1 job, the op STRUCTURE_TEST and the
control panel's button; the STRUCTURE TEST LINE and its LAPSED
mark (2.2.20, 3.3.16, 5.3.47). No external script holds any of
these. TPC gains, built in both residences with vectors: eom_map,
eom_findings, eom_class and eom_register_test (tpc_eom 0.1.0, 403
cases; 2.2.20, 5.3.47), the last taking its record input in the
shape C-16 will carry, fixtures only until then; the D VARIABLE
rules d_variables and d_variable_check, T4's rule for D(x, s, n)
and form_tree, the public parse tree tpc_eom reads, in tpc_form
0.2.0 (2.2.13, 2.2.15); schema 0.5.0 in tpc_zone 0.5.0 (2.2.6,
2.4.7, 2.5.11). [D176.1] [D177.1]
5.1.15 TPC, INCREMENT 10 (D180.3, D186.1; S14, S15). Built in both
residences with vectors: the form's bounds and the computed
exponent's bound in tpc_form 0.2.0 (2.2.13, 2.2.15, 2.2.17); a
DIMENSION's exponent bound in tpc_zone 0.5.0 and tpc_units 0.1.1
(2.5.12, 3.2.11); sr3_scope, the interim scope of SR3 and SR8, in
tpc_strike 0.2.0 (4.4.13); the PROMPT LINT (5.1.13); the
structure check, the D VARIABLE rules and schema 0.5.0 (5.1.14);
the ENVIRONMENT MODULE functions (5.1.16). Every function of
5.1.5, 5.1.11-5.1.14 and 5.1.16 is in the one TPC tree of
increment 10, 28 corpora, 5,083 cases, both residences
byte-identical, all passing under Python 3.8, 3.10, 3.11, 3.12
and 3.13 and PHP 8.4; the Windows run is owed. Each version named
here is a proposed label until H-DECL declares a TPC-PY version
carrying it (5.11.9). [D180.3] [D186.1] [S14] [S15]
5.1.16 PLACEMENT RULE AND TPC, ENVIRONMENT MODULES (D178.1). The
placement rule of 5.1.3 also names: the interview's checks and
its rounds; the expansion and the re-expansion of MODULES USED;
the CATALOGUE STATE at every MODULE DECLARATION; the checks of
the modules page; the ENVIRONMENT MODULE pages and the proposal
pages; the statuses shown to the author, to H-DECL and on the
control panel; the MODULE USE VIEW (5.22, 5.3.48). No external
script holds any of these. TPC gains, built in both residences
with vectors (tpc_module 0.1.0, 414 cases): module_parse and
module_digest (5.22.2), module_bind and module_expand (5.22.7),
module_verify (5.22.8), interview_check and not_included_lines
(5.22.5, 5.22.6), catalogue_state (5.22.10), module_check
(5.22.11), draft_module_status (5.22.14) and module_use_view
(5.22.16). [D178.1]