privacy · proofs · compute
v2.0 · checksummed

Map. Reader's Map

v2.0
Cite this section

Copy/paste (plain text):

Jason St George. "Map. Reader's Map" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v2.0. /v/2.0/read/front-matter/readers-map/

Reader’s Map

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 the following table as your compass:

Layer Role in the Stack Primary Sections Key Metrics / Concepts Falsification Test
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](/v/2.0/read/part-iii/14-layer-0/) Layer 0 (open hardware, profiles, lot sampling, FERs); [§28: Implementation Sketches for Builders](/v/2.0/read/part-vi/28-implementation-sketches/) (L0 implementation sketches); [Appendix D: Energy & Plant Architecture](/v/2.0/read/appendix/d-energy-plant/) (Energy & Plant); [Appendix E: Hardware Profiles](/v/2.0/read/appendix/e-hardware-profiles/) (Hardware Profiles)

Hardware profiles (HIDs); lot-sampling coverage; Facility Energy Receipts (FERs); Facility Capacity Receipts (FCRs); sovereign optionality 𝒪s; Physical VerifyPrice (infra audit); disruption-adjusted VerifyPrice; PUE/ERE/WUE; kWh/receipt; profile incidents

RL10 (physical opacity) or RL13 (𝒪snet 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](/v/2.0/read/part-iii/15-layer-1/) Layer 1 (threats, design rules, mechanisms, VerifyReach); [§28: Implementation Sketches for Builders](/v/2.0/read/part-vi/28-implementation-sketches/) (comms sketch); [Appendix F: Communications Resilience Mechanisms](/v/2.0/read/appendix/f-comms/) (Comms Resilience)

VerifyReach(N,R): p50/p95 time-to-first-connection; succ1/succ2 reachability; failure causes; share encrypted/obfuscated traffic; peer-set diversity (geo/ASN); swap success 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](/v/2.0/read/part-iii/16-layer-2/) Layer 2 (threats, design rules, multi-home architecture, update pipeline, key mgmt, fallback playbooks); [§28: Implementation Sketches for Builders](/v/2.0/read/part-vi/28-implementation-sketches/) (distribution tooling); [Appendix B: Practical KPIs & Telemetry Templates](/v/2.0/read/appendix/b-telemetry-templates/) (update KPIs)

Update health: p50/p95 metadata & artifact fetch times; success/rollback/signature-failure rates; mirror/CDN top-N share; geographic/ASN diversity; key-rotation & incident history

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](/v/2.0/read/part-iii/17-layer-3/) Layer 3 (identity kernel, human & machine identity, reputation, guardrails, how identity uses the loop); [§24: Legal, Policy, and Jurisdictional Posture](/v/2.0/read/part-v/24-legal-policy-posture/) (lawful-privacy requirements); [Appendix C: The SDK (Proofs-as-a-Library)](/v/2.0/read/appendix/c-sdk/) (PaL/PRK SDK)

Identity-predicate VerifyPrice (p50/p95 verify times for age/residency/set-membership proofs); unlinkability tests; reputation from PIDL receipts (SLA fulfillment vs slashes); hardware-anchored machine attestations

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: [§9: Compute Through the "AI Money" Lens](/v/2.0/read/part-ii/9-compute-as-ai-money/) Compute Through the “AI Money” Lens, [§10: Work Credits: Energy-Anchored Claims](/v/2.0/read/part-ii/10-work-credits/) Work Credits; Structural: [§18: From Infrastructure to Economics](/v/2.0/read/part-iv/18-infrastructure-to-economics/) Infrastructure to Economics; [§19: Layer 4: Truth & Work](/v/2.0/read/part-iv/19-layer-4/) Layer 4 (canonical workloads, PoUW, proof factories, PaL); [§21: The Modular Stack](/v/2.0/read/part-iv/21-modular-stack/) (primitive catalog); [Appendix A: Formal Model of Verification Asymmetry & VerifyPrice](/v/2.0/read/appendix/a-verifyprice-model/) (formal VerifyPrice)

(W) per workload: p50/p95 verify times/costs; failure rates; r(W) = v(W)/p(W); prover concentration; SLA attainment (Bronze/Silver/Gold); MatMul-PoUW economics; Work-Credit issuance

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 the service markets described by the legacy “Private Money,” “AI Money,” and “Proof/Attestation Money” lenses settle; their Work Credits and capacity instruments remain typed service claims. The separate base asset is the only conditional monetary candidate.

Analytical lenses: [§7: Privacy as Private Money](/v/2.0/read/part-ii/7-privacy-as-private-money/) Privacy as Private Money, [§9: Compute Through the "AI Money" Lens](/v/2.0/read/part-ii/9-compute-as-ai-money/) AI Money, [§8: Proofs as Attestation Money](/v/2.0/read/part-ii/8-proofs-as-attestation-money/) Proof/Attestation Money; service claims: [§10: Work Credits: Energy-Anchored Claims](/v/2.0/read/part-ii/10-work-credits/) (Work Credits); Stack: [§20: Layer 5: Value & Settlement](/v/2.0/read/part-iv/20-layer-5/) Layer 5 (settlement as workload, PRK, bridge-safety, corridors); [§21: The Modular Stack](/v/2.0/read/part-iv/21-modular-stack/) (treasury/payroll, media, inference, procurement flows); [§28: Implementation Sketches for Builders](/v/2.0/read/part-vi/28-implementation-sketches/) (privacy toolkit); [Appendix F: Communications Resilience Mechanisms](/v/2.0/read/appendix/f-comms/) (swaps, routing)

(C): swap success target; refund_safe(C) = 1.0; p50/p95 time-to-finality; anonymity-set size & churn; corridor LP/route concentration; non-custodial vs custodial flow share

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: [§19: Layer 4: Truth & Work](/v/2.0/read/part-iv/19-layer-4/) (VerifyPrice observatory); [§23: Extended Telemetry](/v/2.0/read/part-v/23-extended-telemetry/) Extended Telemetry; Governance: [§22: Layer 6: Governance & Telemetry](/v/2.0/read/part-v/22-layer-6/) Layer 6 (SLOs as constitution, control surfaces, Bell-Labs vs on-chain vs norms); Legal: [§24: Legal, Policy, and Jurisdictional Posture](/v/2.0/read/part-v/24-legal-policy-posture/); Ops: [§25: Operator & Investor Checklist](/v/2.0/read/part-v/25-operator-investor-checklist/) (checklist & red flags); Dynamics: [§26: Adoption Curve & Ecosystem Dynamics](/v/2.0/read/part-vi/26-adoption-curve/) and [§27: Risk Analysis & Failure Modes](/v/2.0/read/part-vi/27-risk-analysis/); [Appendix A: Formal Model of Verification Asymmetry & VerifyPrice](/v/2.0/read/appendix/a-verifyprice-model/) and [Appendix B: Practical KPIs & Telemetry Templates](/v/2.0/read/appendix/b-telemetry-templates/)

VerifyPrice dashboards per workload; VerifyReach & VerifySettle boards; VerifyFlow (market realization); twelve public boards or maps ([§23: Extended Telemetry](/v/2.0/read/part-v/23-extended-telemetry/)), including native-buyer, common-cause, and sponsor-dependency telemetry; decentralization metrics; fee+burn coverage; Wrapper Dominance; agency preservation

Receipt datasets unverifiable or controlled by single party; wrapper-led price without native use (interpret via VerifyFlow, not as sole red line)

Readers who want the version history—what each release from v1.2 onward added, and why—will find it in Appendix J: What Changed Across Releases. It is not needed to read the argument.

Tip: hover a heading to reveal its permalink symbol for copying.