Map. Reader's Map
Copy/paste (plain text):
Jason St George. "Map. Reader's Map" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v1.5. /v/1.5/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.
v1.2 additions: Layer 0 now includes Facility Capacity Receipts (§14.5.1) and Physical VerifyPrice (§19.7.4); Layer 6 telemetry now includes the Wrapper Dominance Board and Agency Preservation Board (§23.1). A new political-economy thread runs through Part I: the Treasury Market as Control Panel (§2.1.1), the Participation Line (§2.4), Administrative Repression (§4.2), and AI Homestead vs. Enclosure (§4), culminating in a ninth SoV requirement, agency preservation (§3), and the closing frame Equip, Don’t Manage (§31).
A second v1.2 thread runs around the stack rather than through it. The Market Realization Plane (§6.5) models how external financial wrappers — ETFs, treasury companies, custodians, derivatives, dealers, and systematic allocation rules — represent claims on the native asset, and the Market-Price Non-Equivalence Corollary (§6) establishes that price appreciation and monetary adoption imply each other in neither direction. This adds a fourth verification family, VerifyFlow (§23.1.1), a corresponding public board, a compositional adversary class that requires no hostile actor (§4.2), a third boundary tension between institutional holdability and native monetary function (§4.5), a split of allocator adoption into native (Phase II-A) and wrapper-led (Phase II-B) paths, Market Realization Warnings distinct from monetary red lines (§27.2), and the formal flow model in Appendix H. Readers who want only the conceptual payload can read §6 (value capture vs. price capture) and §31 (two loops, not one) and skip the appendix entirely.
Use this table as your compass:
| Layer | Role in the Stack | Primary Sections | Key Metrics / Concepts | Falsification Test |
|---|---|---|---|---|
| Layer 0 – Verifiable Machines & Energy | Physical base reality: open silicon, sampled supply chains, and the power plants that keep provers and routers alive. For pure proof correctness, sound cryptography should tolerate untrusted provers. Layer 0 becomes essential when claims include physical capture, energy use, machine identity, witness confidentiality, or useful-work fairness. | §14 Layer 0 – Verifiable Machines & Energy (open hardware, profiles, lot sampling, FERs); §14.9 (Sovereign Optionality O_s); §14.10 (Resilience vs Affordability, disruption-adjusted VerifyPrice); §28.1 (Layer-0 implementation sketches); Appendix D (Energy & Plant); Appendix E (Hardware Profiles). | Hardware profiles (HIDs); lot-sampling coverage; Facility Energy Receipts (FERs); Facility Capacity Receipts (FCRs); sovereign optionality O_s; Physical VerifyPrice (infra audit); disruption-adjusted VerifyPrice; PUE/ERE/WUE; kWh/receipt; profile incidents. | RL10 (physical opacity) or RL13 (O_s^net below threshold / rationing jurisdictions); hinge VerifyPrice becomes sovereign-policy-driven |
| 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. | >20% ASNs unreachable for >7 days |
| 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). | Single key compromise can push malicious 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. | Identity requires centralized issuer |
| 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. | VerifyPrice p95 exceeds SLO for ≥3 months |
| 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). | Corridor refund_safe < 100% (repeated) |
| 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). | Receipt datasets unverifiable or controlled by single party |
Tip: hover a heading to reveal its permalink symbol for copying.