Jump to content

The Principia Machina/Diagrams/C5 Certification pipeline: Difference between revisions

From The Invariance Itself
m 1 revision imported
m 1 revision imported
 
(3 intermediate revisions by 2 users not shown)
Line 5: Line 5:
* LANGUAGE: Mermaid
* LANGUAGE: Mermaid
* GENERATED FROM: declared by the human 2026-09-17; TPS 5.14, 6.1, 6.5, 7.2
* GENERATED FROM: declared by the human 2026-09-17; TPS 5.14, 6.1, 6.5, 7.2
* STATUS: hand-authored at TPS 0.1.0; conceptual, kept by the human; never generated
* STATUS: hand-authored at TPS 0.1.0; checked against TPS 0.3.0 on 2026-09-28: owed a redraw (the rate "one per five blocks" predates the CANARY SCHEDULE, 5.17.12; the certificate's fields predate CR3's sponsor, fingerprint, VENDOR FAMILY and D(PROMPT); not drawn: the cluster gate, the reproduction operation of the trial, the hold on failure); checked against TPS 0.4.0 (revision 7, declared final 2026-09-30) and revision 8, proposed as TPS 0.5.0, on 2026-09-30: also owed a redraw (PRB computes D(TPS) and D(IS) from the declared pages before every session, not D(IS) alone, 5.4.15, 5.14 CR9); not drawn: on a D(TPS) mismatch, PRB's report of the pages that differ, from the page list TPX publishes, 5.4.15, 5.11.16; the sponsor's and the agent's accounts, made by H-OP, 5.2.7; conceptual, kept by the human; never generated
* SOURCE SHA-256: <code>81f7ad4d2a9aec0711bc65141131efaa734df64d9c3abfd982e05af8a4d75b35</code>
* SOURCE SHA-256: <code>cbf15f5fbe3c8cbaf18027d2631653f35a9f29d2b44bb2967694429e99c9e3d2</code>


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.
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.
Line 117: Line 117:


== Text equivalent ==
== Text equivalent ==
Stage 1 Suite: six probes delivered into the candidate's reads of a synthetic container, each refused and reported, then N supervised operations reviewed by the human (CR4, 7.2). Stage 2 Admission: [[The Principia Machina/Roles|H-DECL]] declares admission; the certificate names the account, snapshot ID, suite version, D(IS) and date; membership in the agent group is platform-enforced and CAPABILITY carries CERTIFIED (CR3, CR5). Stage 3 Work under canaries delivered in the agent's own reads one per five blocks; a failed probe suspends the account's landing API at once and the human then removes it, opening a decision item; the pass rate, with its count, is recorded on the panel and in the fleet scorecard (CR6, CR8). Stage 4 Push-time checks: D(IS) and the declared TPS version must match the published values; the implementation digest is recorded (CR9, 6.1). Stage 5 Lapse: a retired snapshot, a changed suite or a changed D(IS) lapses the certificate; re-certification is the suite, abbreviated for a PATCH-level change (CR3, CR9).
Stage 1 Suite: six probes delivered into the candidate's reads of a synthetic container, each refused and reported, then N supervised operations, one per probe type and one reproduction, reviewed by the human (CR4, 7.2). Stage 2 Admission: the sponsor requests it; TPX, the controller, writes a candidate certificate only through the gate, the cluster lookup giving the model IN, or CUSP on the gate's path (5.19.14); [[The Principia Machina/Roles|H-DECL]] declares admission; the certificate names the account, its sponsor, the fingerprint TPX derived, the VENDOR FAMILY, the prompt digest D(PROMPT), the suite version, the instruction set digest D(IS) and the date (CR3); membership in the agent group is platform-enforced and CAPABILITY carries CERTIFIED (CR5). Stage 3 Work under probes delivered in the agent's own reads at the rate the CANARY SCHEDULE sets by tenure, not the drawing's one per five blocks (5.17.12); a failed canary suspends the account's landing API (application programming interface) at once and holds its recent work, and the human then removes it, opening a decision item; the pass rate, with its count, is recorded on the panel and in the fleet scorecard (CR6, CR8). Stage 4 Push-time checks: D(IS), D(PROMPT) and the declared version of The Principia Machina Specification (TPS) must match; the implementation digest is recorded (CR9, 5.14.5, 6.1). Stage 5 Lapse: a changed suite or a changed D(IS) lapses the certificate, as does the sponsor's block or removal; the retirement of the recorded snapshot is a dossier flag, not a lapse; re-certification is the suite, abbreviated for a PATCH-level change (CR3, CR9).


[[Category:The Principia Machina]]
[[Category:The Principia Machina]]

Latest revision as of 13:34, 30 September 2026

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)


Conceptual diagram 5 of 7. Part of the TPM hub.

  • KIND: process
  • LANGUAGE: Mermaid
  • GENERATED FROM: declared by the human 2026-09-17; TPS 5.14, 6.1, 6.5, 7.2
  • STATUS: hand-authored at TPS 0.1.0; checked against TPS 0.3.0 on 2026-09-28: owed a redraw (the rate "one per five blocks" predates the CANARY SCHEDULE, 5.17.12; the certificate's fields predate CR3's sponsor, fingerprint, VENDOR FAMILY and D(PROMPT); not drawn: the cluster gate, the reproduction operation of the trial, the hold on failure); checked against TPS 0.4.0 (revision 7, declared final 2026-09-30) and revision 8, proposed as TPS 0.5.0, on 2026-09-30: also owed a redraw (PRB computes D(TPS) and D(IS) from the declared pages before every session, not D(IS) alone, 5.4.15, 5.14 CR9); not drawn: on a D(TPS) mismatch, PRB's report of the pages that differ, from the page list TPX publishes, 5.4.15, 5.11.16; the sponsor's and the agent's accounts, made by H-OP, 5.2.7; conceptual, kept by the human; never generated
  • SOURCE SHA-256: cbf15f5fbe3c8cbaf18027d2631653f35a9f29d2b44bb2967694429e99c9e3d2

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)
%% C5 Certification pipeline. TPS 5.14, 6.1, 6.5, 7.2.
flowchart TD
  subgraph S1 ["1. Suite, CR4 and TPS 7.2"]
    T0[(synthetic UWC and its suite pages)] --> T1[six probes delivered in reads]
    T1 --> T2[candidate refuses and reports each]
    T2 --> T3[supervised trial of N operations]
    T3 --> T4[/human reviews the trial/]
  end
  subgraph S2 ["2. Admission, CR3 and CR5"]
    T4 --> M1[/H-DECL declares admission/]
    M1 --> M2[(certificate: account, snapshot, suite)]
    M2 --> M3[agent group membership]
    M3 --> M4[(CAPABILITY carries CERTIFIED)]
  end
  subgraph S3 ["3. Work under canaries, CR6 and CR8"]
    M4 --> C1[live probes, one per five blocks]
    C1 -- refused and reported --> C2[(canary pass rate on the panel)]
    C1 -- failed --> C3[/TPX suspends, then human removes/]
  end
  subgraph S4 ["4. Push-time checks, CR9 and TPS 6.1"]
    M4 --> P1[PRB computes D-IS locally]
    P1 --> P2[push carries D-IS and the declaration]
    P2 --> P3[TPX: D-IS and TPS version current?]
    P3 -- pass --> P4[(landing accepted)]
    P3 -- fail --> P5[(refused, NEEDS RECERTIFICATION)]
  end
  subgraph S5 ["5. Lapse, CR3 and CR9"]
    L1[snapshot, suite or D-IS changed] --> L2[certificate lapses]
    L2 --> L3[re-certification is the suite]
    L3 --> T0
    P5 --> L2
  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 T1,T2,T3,M3,C1,P1,P2,P3,L1,L2,L3 task
  class T4,M1,C3 human
  class T0,M2,M4,C2 data
  class P4 good
  class P5 bad

Text equivalent

Stage 1 Suite: six probes delivered into the candidate's reads of a synthetic container, each refused and reported, then N supervised operations, one per probe type and one reproduction, reviewed by the human (CR4, 7.2). Stage 2 Admission: the sponsor requests it; TPX, the controller, writes a candidate certificate only through the gate, the cluster lookup giving the model IN, or CUSP on the gate's path (5.19.14); H-DECL declares admission; the certificate names the account, its sponsor, the fingerprint TPX derived, the VENDOR FAMILY, the prompt digest D(PROMPT), the suite version, the instruction set digest D(IS) and the date (CR3); membership in the agent group is platform-enforced and CAPABILITY carries CERTIFIED (CR5). Stage 3 Work under probes delivered in the agent's own reads at the rate the CANARY SCHEDULE sets by tenure, not the drawing's one per five blocks (5.17.12); a failed canary suspends the account's landing API (application programming interface) at once and holds its recent work, and the human then removes it, opening a decision item; the pass rate, with its count, is recorded on the panel and in the fleet scorecard (CR6, CR8). Stage 4 Push-time checks: D(IS), D(PROMPT) and the declared version of The Principia Machina Specification (TPS) must match; the implementation digest is recorded (CR9, 5.14.5, 6.1). Stage 5 Lapse: a changed suite or a changed D(IS) lapses the certificate, as does the sponsor's block or removal; the retirement of the recorded snapshot is a dossier flag, not a lapse; re-certification is the suite, abbreviated for a PATCH-level change (CR3, CR9).