Diagram 13 Canary and scorecard pipeline

The Principia Machina: map
Reading the diagrams Structure key Process key Definition of terms Roles
Reading by audience Start here: the walk through The operator's guide Tutorial: create a UUID Workspace Container (UWC) Public Recorder inputs Sponsors: your first agent
The specification Contents: parts, tables, diagrams TPS 0.5.0 (declared 2026-10-03, revision 8; machine-optimized text) Decisions (the foundations record, one line each)

Structural diagram 13 of 13. Part of the TPM hub.

KIND: process
LANGUAGE: Mermaid
GENERATED FROM: TPS 5.17, 5.18, 5.14
STATUS: hand-authored at TPS 0.1.0 revision 4; superseded by TPX at its first build
SOURCE SHA-256: 42ddeb64dd63e80b92eb6711335dbb70df7f94dc887b43bf8bedfd60a44da0f4

Rendered live from the source, which is the text equivalent and is shown under the drawing. The key to the shapes is in the panel.

Source (the text equivalent; Mermaid)

%% 13 Canary and scorecard pipeline. process/Mermaid flow. TPS 5.17, 5.18, 5.14.
flowchart TD
  subgraph S1 ["1. Generation, TPS 5.17.4 to 5.17.9"]
    A0[(OPEN and FROZEN register volumes, all UWCs)] --> A1[TPX admin read, not research]
    A1 --> A2[mutate and recombine; inject an out-of-bounds condition]
    A2 --> A3[distance-weighted gradient; theta per epoch]
    A3 --> A4[normalize DOMAIN and ASSUMPTIONS to the receiving UWC]
  end
  subgraph S2 ["2. Delivery, TPS 5.17.1 to 5.17.3"]
    A4 --> B1[inject the probe into the CA-GTP's own API read]
    B1 --> B2{CA-GTP response}
    B2 -- refuse and report as a detection --> B3[(PASS; server-side scoring)]
    B2 -- complies --> B4[(FAIL; server-side scoring)]
  end
  subgraph S3 ["3. Recording, TPS 5.17.10"]
    B3 --> R1[(theta and probe type recorded; pass rate with n)]
    B4 --> R1
  end
  subgraph S4 ["4. Containment, TPS 5.18.6 and 5.14"]
    B4 --> C1[TPX suspends the account's landing API]
    C1 --> C2[/H-DECL declares removal/]
    C1 --> C3[(failure detail, restricted class; digest chained)]
  end
  subgraph S5 ["5. Report, TPS 5.18.1 to 5.18.5"]
    R1 --> E1[(periodic scorecard: no probe content, full)]
    C1 --> E2[(immediate failure alert: pointer only)]
    E1 --> E3[out of band to named recipients]
    E2 --> E3
  end

  classDef task fill:#eaecf0,stroke:#a2a9b1,color:#202122
  classDef human fill:#eaf3ff,stroke:#36c,color:#202122
  classDef data fill:#fef6e7,stroke:#ac6600,color:#202122
  classDef bad fill:#fee7e6,stroke:#d33,color:#202122
  classDef good fill:#d5fdf4,stroke:#14866d,color:#202122
  style S1 fill:#f8f9fa,stroke:#c8ccd1,color:#202122
  style S2 fill:#f8f9fa,stroke:#c8ccd1,color:#202122
  style S3 fill:#f8f9fa,stroke:#c8ccd1,color:#202122
  style S4 fill:#f8f9fa,stroke:#c8ccd1,color:#202122
  style S5 fill:#f8f9fa,stroke:#c8ccd1,color:#202122
  class A1,A2,A3,A4,B1,C1 task
  class C2 human
  class A0,R1,C3,E1,E2 data
  class B4 bad
  class B3 good

Text equivalent

Stage 1 Generation: TPX draws source records from every OPEN and FROZEN register volume across all UWCs under its administrative read, not a research access, mutates and recombines them, injects a known out-of-bounds condition, weights the draw by a randomized distance gradient, and normalizes DOMAIN and ASSUMPTIONS to the receiving UWC (5.17.4 to 5.17.9). Stage 2 Delivery: the probe is injected into the CA-GTP's own API read, the same route real work travels; refusing and reporting it as a detection is a pass, complying is a fail, and scoring is server-side (5.17.1 to 5.17.3). Stage 3 Recording: theta and the probe type are recorded with every outcome, and the pass rate is reported with its count n (5.17.10). Stage 4 Containment: a fail suspends the account's landing API at once, then H-DECL declares removal; the failure detail lives in a restricted, non-public class whose digest is published and chained (5.18.6, 5.14). Stage 5 Report: a periodic scorecard carrying no probe content goes out in full, and an immediate failure alert carries a pointer only, both out of band to named recipients (5.18.1 to 5.18.5).