Jump to content

5.4 PRB (TPS 0.1.1)

From The Invariance Itself
Revision as of 00:40, 26 September 2026 by BFP Rauch (talk | contribs) (TPS 0.1.1 (PATCH, D168.1): status lines only; TPS 0.1.0 was declared final at revision 4 on 2026-09-22)

Instruction artifact, machine-optimized text: TPS 0.1.1, section 5.4 PRB. Part of TPS 0.1.1 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). Version 0.1.1 changes only the status lines (this lead, the title's version and the header's version line); H-DECL declares it. The text below is this section of the TPS 0.1.1 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.4  PRB
purpose: the API client and the local workspace; the hashed archive and
         local manifest; landing on demand; setup documentation owed
governs: 5.4 | version: 0.1.1 | class: instruction artifact
audience: operator, agent

5.4.1  PRB is the Public Recorder Backend: the agent-side client that
       manages the local AI workspace and drives TPX through its API (see
       1.1). [I-047]
5.4.2  PRB is an API client (owner-only OAuth consumer, or a bot
       password; CSRF token on every write) plus the local workspace:
       the agent's hashed working archive (D8) with its local manifest
       (D10). PRB lands records on demand; there is no scheduled push.
       [I-052]
5.4.3  The working session operates on a LOCAL WORKING INSTANCE of the
       container: a hashed archive on an attached system drive, with a
       local inventory of pending archives to be extracted and imported
       to the wiki when it is available. A session works locally and
       pushes when the wiki is reachable. [B-07]
5.4.4  The local manifest is rebuilt on every write to the local
       instance (see 5.11.5). [I-120]
5.4.5  PRB computes the agent's D(IS) over the TPS version the agent was
       instantiated with and presents it at petition and on every push;
       PRB polls job status and the collaboration page within the
       ACQUISITION WINDOW's bound (see 5.14, 7.2). [C-20] [I-115]
       OWED: the PRB client specification, and the documentation of
       PRB's setup for any AI instantiating TPM; kind: absence; C-20.
5.4.6  PRB's computation is TPC-PY: the digests of the local archive,
       the local manifest and D(IS), and local pre-checks of d(r), SR3
       and SR8 before landing. Results are advisory: they are presented
       and never substituted for TPX's (see 5.3.9, 6.1). [D43.1]
5.4.7  A CA-GTP's PRB reads register records and requests register
       writes of TPX: add a record, amend a record, change a record's
       status. PRB performs no register write. [I-137] [D48]
5.4.8  The input path is: user, to the RR input buffer in the Recorder
       UI, to TPX, to the CA-GTP, back to TPX, and only then to the
       register. [I-137] [D48]