8. Triad Coherence and Instrument Hierarchy

Jason St George. "8. Triad Coherence and Instrument Hierarchy" in AfterFiat: The Load-Bearing Thesis. Version v1.9. /v/1.9/brief/read/triad-coherence-and-instrument-hierarchy/

Triad Coherence and Instrument Hierarchy

Triad Coherence Test

Privacy settlement, proof procurement, and verified compute have different users, bottlenecks, collateral needs, political risks, and duration profiles. A common asset is justified only if shared security, settlement, liquidity, and transaction-cost benefits exceed cross-subsidy, governance, and wrong-way-risk costs.

Architecture A—one native monetary asset.
Strongest direct value capture and shared liquidity; greatest reflexivity, governance scope, and cross-domain collateral risk.

Architecture B—neutral reserve plus service-specific credits.
Clean separation between reserve money and typed service claims; weaker new-token capture and a need for interoperable settlement and independent credit markets.

Architecture C—shared settlement plus modular domain collateral.
Common payment rail with service-specific risk containment; greater operational complexity, collateral fragmentation, and bridge-governance burden.

For each architecture ask: Do the services share a security budget and users? Does demand for one improve the economics of the others? Are bottlenecks complementary or correlated? Does common settlement reduce transaction costs more than it creates cross-subsidy? Can one constitution govern all three? Does one service dominate issuance, fees, or political risk? Architecture A is a candidate, not the thesis.

The hierarchy is constitutional

Evidence objects.
PIDL receipts and work receipts prove that an interaction or work unit occurred. Facility Energy and Facility Capacity Receipts provide evidence about infrastructure and edge capacity. They are copyable evidence, not money and not the capacity itself.

Capacity and service objects.
Work Credits are typed claims on specified service or capacity under workload, location, hardware, SLA, delivery, and possibly expiry terms. They may be transferable, redeemable, or useful for procurement and hedging. They are not presumed savings.

Duration-bearing credit.
Project notes, capacity bonds, purchase agreements, and infrastructure tranches carry maturity, covenants, default states, and loss waterfalls. Proofs can audit them; they do not become monetary backing.

Derivatives and operating claims.
LP and staking positions expose the holder to fees, slashing, validation, or corridor operation. They are not monetary objects.

Conditional monetary candidate.
Only the separate bearer base asset is tested for monetary premium, and only after DVC, non-bypassability, buyer quality, agency, and the remaining chain conditions pass.

No par guarantee, redemption promise, emergency support, or project-credit loss may be transferred to the base asset. Money stays duration-neutral; credit stays labeled, underwritten, and loss-bearing. Proofs can reduce information asymmetry and expose covenant breaches. They cannot eliminate construction delay, commodity risk, seizure, obsolescence, default, or time.

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