§13. SoV Evaluation Framework

Jason St George. "§13. SoV Evaluation Framework" in Next Generation Stores of Value: Privacy, Proofs, Compute. Version v3.2. /v/3.2/read/part-ii/13-sov-evaluation-framework/

SoV Evaluation Framework

Later, Part V will present an operator/investor checklist that spans the whole stack. Here we sketch the monetary lens: how to evaluate whether the base asset is a credible store-of-value candidate while keeping the service and evidence instruments beneath it analytically separate.

Understand what you are doing when you run it. You are not scoring a product; you are auditing a supply chain that runs in two directions at once — upward from machines into money, and outward from one balance sheet to whoever is standing behind it. Every question below is a way of asking one of two things: can this thing deliver what it promises under the conditions that make it valuable? and who absorbs the loss when it cannot? The first is the question a buyer asks; the second is the question an underwriter asks. A store of value has to survive both, which is why the checklist reads as though written by two people.

One distinction does more work than any other here, so it belongs at the front rather than buried as a note: legibility is not resilience. A facility can be perfectly transparent about being catastrophically fragile — publish every receipt, pass every audit, display its full telemetry, and still fail on the first stressed day. The reverse is rarer but real: a robust operation whose interior is opaque. Every measurement regime, this thesis’s included, is biased toward the first thing it can see; dashboards reward the visible. So the checklist deliberately separates the questions that ask can the substrate be seen from the ones that ask can what we see withstand anything, and treats a high score on the first set as establishing nothing at all about the second. Items 10 and 11 exist as two items for exactly this reason. Passing the legibility questions makes an asset auditable; only the resilience questions can make it a store of value.

For a candidate base asset $X$, ask:

1. What triad services does it route value from?

   • Exactly which Privacy, Proof, and Compute flows pay fees, burn supply, or require base-asset collateral?

   • Are those workloads canonical and well-specified?

   • Are the associated Work Credits reported as typed service claims rather than counted as monetary holdings?

2. How is base-asset issuance constrained?

   • Is issuance formulaic and transparent, and distinct from Work Credit issuance against DVC?

   • Can governance mint outside of those rules? Under what constraints?

3. Can anyone verify the service linkage?

   • Are VerifyPrice and workload telemetry public?

   • Can a third party recompute DVC and sample the proofs, settlements, and Work Credit claims that justify fee and collateral activity?

4. How does it behave under repression?

   • If real yields are $-300$ bps for 3 years, what happens to demand for $X$?

   • If on-/off-ramps are throttled, can $X$ still be acquired, held, and spent?

5. Is privacy lawful by design?

   • Are there clean paths for voluntary disclosure that do not reintroduce custody or KYC chokepoints?

   • Are the receipts (PIDL) expressive enough for auditors?

6. What is the duration profile?

   • Does $X$ promise fixed nominal coupons (bond-like) or variable participation in fee flows (equity/commodity-like)?

   • Can a sovereign push its real return negative by fiat?

   • If $X$ is duration-neutral as money, what separate instrument, if any, is supposed to warehouse the construction interval of the physical assets the stack requires? Conflating the two is a completeness failure, not a feature (§2: The World Forces New Monetary Primitives, §30: Objections & Responses).

7. Who can be locked out?

   • Is access to $X$ gated by one jurisdiction, cloud, or app store?

   • Do Layer-0/1/2 assumptions create hidden chokepoints?

8. Can users bypass the asset?

   • Can users buy equivalent Privacy, Proofs, or Compute service for fiat, stablecoins, or direct cloud contracts without touching the asset?

   • Are fees actually paid in the native asset, or do operators accept and immediately off-ramp alternatives?

   • Are burns and collateral lockups material, or negligible relative to total supply?

9. Can institutions legally and operationally hold it?

   • Is custody support available from regulated custodians?

   • Is the legal classification clear enough for treasury or fund mandates?

   • Is liquidity deep enough for institutional-scale positions?

   • Does governance redirect value away from holders?

10. Is the physical infrastructure behind it legible?

    • Are Facility Capacity Receipts (§14: Layer 0: Verifiable Machines & Energy) available and independently verifiable for a material share of active capacity?

    • Is Physical VerifyPrice (§19: Layer 4: Truth & Work) within published bounds, or does verifying the facility take months of trust-the-vendor diligence?

    • Is supply concentrated in a small number of hyperscalers, closed TEEs, or single-jurisdiction facilities (Homestead Ratio / Enclosure Risk Flag, §4: Threat Model)?

11. Is that infrastructure resilient, or merely visible?

    • What is network sovereign optionality, $\mathcal{O}_s^{\text{net}}$ (§14: Layer 0: Verifiable Machines & Energy), and is it published with its component vector and weights rather than as a bare scalar?

    • What share of VerifyPrice-tracked capacity sits in jurisdictions with an active curtailment, rationing, or interconnection-denial regime (§4: Threat Model)? Is Red Line 13 approaching?

    • Is the headline verification cost a benign-state figure, or is disruption-adjusted VerifyPrice published alongside it with stated disruption probabilities (§14: Layer 0: Verifiable Machines & Energy)?

    • Does the resilience premium demonstrably lower disruption-adjusted cost, or is it capital misallocation with a security narrative attached (§14: Layer 0: Verifiable Machines & Energy)?

    This is the pair to the previous question, and an operator will try to collapse them. The prior question asks whether the substrate can be seen; this one asks whether what we see can withstand anything — the distinction opened at the head of this chapter, and the reason Red Lines 10 and 13 are separate.

12. Is demand wrapped, or protocol-native?

    • What share of economic exposure sits in ETFs, treasury companies, and custodial wrappers versus protocol-native settlement (Wrapper Dominance Ratio, §10: Work Credits: Energy-Anchored Claims)?

    • Is price rising while native fee share, private settlement volume, and collateral lockups stagnate?

13. Does it equip holders, or manage them?

    • What share of flows are non-custodial and require no global identity (§3: First Principles: What a SoV Must Survive)?

    • Does disclosure stay selective (predicates) rather than converging into a reconstructable dossier (§24: Legal, Policy, and Jurisdictional Posture)?

A base asset that scores well on these questions remains a next-generation SoV candidate:

• It is backed by verifiable work, not by decree.

• Its value is rooted in capacities that a digital civilization must keep buying: privacy, proofs, and compute.

• It is measurable under stress via telemetry, not defended by rhetoric.

Comparison: Traditional Hard Assets vs. the Base-Asset Candidate

For context, it is useful to compare how gold and silver—the canonical “old-world” stores of value—score against the same framework:

SoV comparison: traditional hard assets vs. the conditional triad base-asset candidate. Work Credits are excluded because they are typed service claims.

Gold and silver excel on Lindy (millennia of history), simplicity (no software, no network), and zero counterparty risk in physical form. They remain rational holdings during the transition window while the triad stack matures. Healthy VerifyPrice, VerifyReach, VerifySettle, DVC, and native-buyer telemetry can establish distinctive digital capabilities; they do not establish that the base asset is superior money or promote Work Credits into savings instruments.

The thesis does not claim gold is obsolete. It claims only that a base asset may earn a distinct premium for preserving agency across specific digital failure modes—financial repression under surveillance, synthetic media, and compute enclosure—if all nine links hold. The bridge is still load-bearing; the candidate remains under test.

The rest of the thesis will shift back to the stack angle (Layers 0–6) and the telemetry angle (VerifyPrice/Reach/Settle, DVC, buyer quality, decentralization, governance). The monetary question stays in the background: every design choice is judged by whether the base asset can preserve agency and satisfy the nine-link chain, while Work Credits stay what §10: Work Credits: Energy-Anchored Claims established them to be — service instruments — under every regime.

New here? Start with the one-minute version.

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