Map. Reader's Map
Copy/paste (plain text):
Jason St George. "Map. Reader's Map" in Next‑Gen Store of Value: Privacy, Proofs, Compute. Version v1.0. /v/1.0/read/front-matter/readers-map/ Reader’s Map: Layers, Sections & Metrics
This thesis is structured as a ladder of seven interlocking layers. Each layer has one or more “home” sections, and most layers also surface in the Create/Compute → Prove → Settle → Verify loop and in the telemetry program.
Use this table as your compass:
| Layer | Role in the Stack | Primary Sections | Key Metrics / Concepts |
|---|---|---|---|
| Layer 0 – Verifiable Machines & Energy | Physical base reality: open silicon, sampled supply chains, and the power plants that keep provers and routers alive. If the machine can lie or cannot stay on, nothing above it matters. | §14 Layer 0 – Verifiable Machines & Energy (open hardware, profiles, lot sampling, FERs); §28.1 (Layer-0 implementation sketches); Appendix D (Energy & Plant Architecture); Appendix E (Hardware Profiles). | Hardware profiles (HIDs); lot-sampling coverage; Facility Energy Receipts (FERs); PUE/ERE/WUE; kWh/receipt; kgCO₂e/receipt; profile incidents/deprecations. |
| Layer 1 – Reachability: Communications & Transport | Keeps packets flowing under DPI, filtering, and shutdowns. Without Layer 1, the loop cannot run and “public verification” becomes theoretical. | §15 Layer 1 – Reachability: Communications & Transport; §15.1–15.5 (threats, design rules, mechanisms, VerifyReach); §28.1 (comms implementation sketch); Appendix F (Comms Resilience Mechanisms). | VerifyReach(N,R): p50/p95 time-to-first-connection; succ₁/succ₂ reachability; failure causes; share of encrypted/obfuscated traffic; peer-set diversity (geo/ASN); swap success & refund safety under network stress. |
| Layer 2 – Distribution & Execution: Software Supply & Runtime | Ensures honest clients and updates can be shipped even when app stores, CDNs, and DNS are weaponized. Protects the code that speaks the protocol and runs PaL/PRK. | §16 Layer 2 – Distribution & Execution (threats, design rules, multi-home architecture); §16.1–16.9 (update pipeline, key mgmt, fallback playbooks, lawful-privacy posture); §28.2 (distribution & corridor tooling); Appendix B (update KPIs). | Update health: p50/p95 metadata & artifact fetch times; success/rollback/signature-failure rates; mirror/CDN top-N share; geographic/ASN mirror diversity; key-rotation & incident history (“no dashboards, no trust” for updates). |
| Layer 3 – Identity & Claims: Humans & Machines Without Doxxing | Lets humans and machines prove capabilities and rights (age, residency, uniqueness, model ownership, device profile) without turning identity into a global dossier. Reputation is receipts, not biographies. | §17 Layer 3 – Identity & Claims (identity kernel, human & machine identity, reputation, guardrails); §17.9–17.11 (how identity uses the loop + SDK sketch); §24.1 (lawful-privacy requirements for identity); Appendix C (PaL/PRK SDK patterns). | Identity-predicate VerifyPrice (p50/p95 verify times & costs for age/residency/set-membership proofs); unlinkability tests; reputation from PIDL receipts (SLA fulfillment vs slashes); share of flows using anon creds vs real-name; hardware-anchored machine attestations per profile. |
| Layer 4 – Truth & Work: Proof Systems and PoUW | Converts expensive work into cheap-to-check receipts. This is where verification asymmetry lives and where VerifyPrice is defined. | Conceptual base: §9 Compute as AI Money and §10 Work Credits (work as collateral); Structural: §18 From Infrastructure to Economics; §19 Layer 4 – Truth & Work: Proof Systems and PoUW (canonical workloads, PoUW patterns, proof factories, PaL); §21.1 (primitive catalog – PaL, workload registry, proof markets); Appendix A (formal VerifyPrice & r(W)). | VerifyPrice(W) for each canonical workload (proofs, MatMul, inference, provenance, settlement): p50/p95 verify times and costs; failure rates; verification overhead r(W) = v(W)/p(W); prover/market concentration; SLA attainment (Bronze/Silver/Gold); MatMul-PoUW economics; Work-Credit issuance vs real workloads. |
| Layer 5 – Value & Settlement: Privacy Rails & Non-Custodial Flow | Moves value non-custodially and privately, with auditability via receipts. This is where “Private Money” and “AI/Proof Money” actually settle and where pay-for-proof/compute flows clear. | Monetary view: §7 Privacy as Private Money and §10 (Work Credits as claims on settlement & proof capacity); Stack view: §20 Layer 5 – Value & Settlement: Privacy Rails & Non-Custodial Flow (settlement as workload, PRK, bridge-safety, lawful-privacy corridors); §21.1 (PRK & bridge templates); §21.2–21.5 (treasury/payroll, media, inference, procurement flows); §28.2 (privacy corridor + treasury toolkit); Appendix F (atomic swaps, routing, wallets). | Settlement quality / VerifySettle(C): swap success ≥ target (e.g. 95%); refund_safe(C) = 1.0; p50/p95 time-to-finality; anonymity-set size & churn in shielded pools; corridor LP/route concentration; non-custodial vs custodial flow share; “zombie corridor” detection (no volume, thin anonymity). |
| Layer 6 – Governance & Telemetry | The immune system and constitution: keeps drift and capture visible and forces responses. Turns “trustlessness” into dashboards and runbooks. | Metrics core: §19.6–19.7 (VerifyPrice observatory & SLOs); §23 Extended Telemetry: VerifyPrice, VerifyReach, VerifySettle (observability regime & boards); Governance & ops: §22 Layer 6 – Governance & Telemetry (SLOs as constitution, control surfaces, Bell-Labs vs on-chain vs norms); Legal/policy: §24; Operator view: §25 (checklist & red flags); Dynamics & risk: §26–§27; Appendix A & B (formal defs + KPI templates). | VerifyPrice dashboards per workload; VerifyReach & VerifySettle boards; decentralization metrics (entry latency, top-N share, Nakamoto coefficients, geo/ASN spread, router/mirror house share); fee+burn coverage of security budget; repression-beta (triad revenue vs macro shocks); incident reports and response times; telemetry honesty (multi-source, reproducible metrics). |
Tip: hover a heading to reveal its permalink symbol for copying.