Canonical Reserve Doctrine · Volume I

SEA Deep Dive

The reported reserve position for future shortfall: earned, held, ring-fenced, and settlement constrained.

IMPLEMENTED WITH OPEN INPUT GAP

What can be paid if something goes wrong?

SEA reports reserve-backed settlement capacity and the position a participant has earned and holds in that reserve. It is not payment for ordinary production, stock, or a separately issued instrument. Treating a reserve position as spendable output would consume the buffer it is meant to preserve.

SEA · reserve coverage for causal commerce

Reserve coverage supports the promise; it does not manufacture the result.

Participants can earn and hold an SEA-denominated reserve position. SEA reports the coverage available behind performance obligations, while independent outcome evidence determines whether any QCU value is settleable.

The simple promise

Define the outcome. Commit the comparison. Measure the difference. Pay only for the portion independently attributable to the intervention.

First question · resource truth

Did the machine perform verified work?

EcoSynQ can answer through QSA. Another provider can use an admitted meter, instrument, telemetry source, or independent verifier. This establishes resource value and its physical ceiling.

Second question · causal truth

Did that intervention cause the purchased outcome?

The preregistered comparator and independent observation determine the attributable effect. Verified activity can exist without becoming causally settleable customer value.

Causal AI · for beginners

Prediction asks what might happen. Causal AI asks what made it happen.

Most AI learns patterns from the past and predicts what is likely next. A pattern can show that two things happened together without proving that one caused the other. Causal AI declares the action and fair comparison first, measures both results, shows its uncertainty, and refuses to claim causation when the evidence is not strong enough. That is why it can support outcome-based payment.

How causal payment works
01

Mandate before execution

The customer fixes the treatment, comparator, desired outcome, time horizon, risk ceiling, proof rules, and maximum settlement before results are known.

02

Provider commits

The selected executor commits its action, environment, control assignment, software, hardware, and execution window before observing the outcome.

03

Independent observation

An admitted measurement provider reports treatment and control outcomes, uncertainty, calibration, missing data, and regime changes.

04

Attribution before payment

crwdUnit estimates the causal effect, grades identifiability, applies evidence and delivery quality, and refuses settlement when the effect cannot be attributed.

Assured mode · EcoSynQ QaaS

The premium assurance implementation

EcoSynQ supplies an integrated path in which QuantumVM executes the admitted intervention, QSA independently measures physical delivery, Quantum Routing moves work through the declared topology, immuDB anchors proof, and SEA reports reserve coverage.

ExecutorQuantumVM
MeasurementQSA
Evidence witnessimmuDB
Live projectionSurrealDB
SettlementQCU
Federated mode · any provider

Keep the infrastructure. Adopt the causal contract.

A provider does not need QuantumVM or QSA to participate. It can use its existing executor, telemetry, verifier, witness, and settlement rail as long as each role is declared, independently identifiable, and capable of producing the canonical evidence contract.

ExecutorRigetti, AWS, Azure, Kubernetes, HPC, QPU
MeasurementLab instrument, auditor, telemetry provider, oracle
Evidence witnessTransparency log, blockchain, trusted database
SettlementQCU, fiat, invoice, stablecoin, internal chargeback
The provider-neutral Causal ABI

Five messages make unlike systems commercially comparable.

1CausalMandateV1Defines the subject, treatment, comparator, outcome, population, horizon, confounders, risk limit, and settlement rule.
2InterventionCommitmentV1Commits the executor, action, control assignment, execution window, and hardware/software identity before the outcome is known.
3ExecutionEvidenceV1Proves what ran, when it ran, its environment, actual inputs and actions, and the hashes of the raw evidence.
4OutcomeObservationV1Reports treatment and control results with units, method, calibration, uncertainty, missing data, and verifier identity.
5CausalEffectReceiptV1Reports estimated effect, confidence interval, assumptions, sensitivity, identifiability, settleable effect, and settlement eligibility.
Value rule

Proof admits value. It never inflates value.

V_QCU = W_physical × U_computational × R_delivery × Q_outcomeQCU_causal = p × max(0, τ̂ − zα·στ) × q_evidence × q_deliveryA_proof = 0 ⇒ V_settleable = 0

Missing, invalid, late, or policy-inadmissible proof makes the result ineligible for settlement. Stronger proof cannot increase the amount charged.

Assurance ladder

One calculation. Clearly graded confidence.

AIndependent executor and verifier; randomized control
BIndependent verifier; matched or synthetic control
CProvider telemetry; independently witnessed
DProvider self-report; observational comparison
RefusedEffect is not identifiable or proof is inadmissible
What any CPU, GPU, QPU, cloud, or machine provider can sell through causal QCU

Quantum advantage

Did a QPU cause a measurable improvement over the best declared classical alternative?

Cloud optimization

Did a scheduling intervention reduce cost without falling below the required reliability floor?

Ledger outcomes

Did a blockchain improve finality, recovery, integrity, or cost over the admitted alternative?

Energy operations

Did a control policy reduce joules, cooling cost, or carbon intensity per completed workload?

Risk reduction

Did an intervention reduce incident frequency, loss severity, downtime, or recovery time?

crwdUnit’s universal service

A neutral causal contract between the customer, the machine that acts, the system that measures, and the rail that settles.

EcoSynQ is the premium assured customer and implementation. Every other provider can join without surrendering technological sovereignty. crwdUnit standardizes attribution, not the provider’s hardware.

Reserve control chain

Gross reserve is progressively constrained into usable settlement capacity.

E_reserve / E_obligated→RCR→B_SEA→G_pool→S_cap→P_final
1
Coverage
RCR = E_reserve ÷ E_obligated
2
Capital adequacy
B_SEA = min(1, RCR), preventing more-than-fully-backed issuance authority.
3
Ring-fenced collateral
G_pool = ρ · E_reserve, with implemented default ρ = 0.30.
4
Usable liquidity
S_cap = φ · G_pool, with implemented default φ = 0.80.
5
Capped settlement
P_final = min(L_settle, S_cap). The claim cannot exceed usable capacity.
Four hard constraints

The reserve cannot be negotiated around by a dashboard operator.

No Over-Promise

VGN_issued ≤ B_SEA · QWU

No Fake Enforcement

E_reserve = 0 implies P_final = 0.

Monotonic Consequence

Worse breaches strictly produce larger liabilities.

One-Way Constraint

Physics → Value → Commitment → Settlement, never in reverse.

Central engineering constraint

The arithmetic is bounded. The reserve input is still declared.

SPECIFIED · NOT YET WIREDE_reserve(T) = ∫ P(t) · m(t) · η(t) dt

This derivation must live inside QSA’s audited boundary. Until it does, E_reserve is an application-layer assertion rather than a canonical measurement.

Doctrine status register

What is proven, implemented, and still open

IMPLEMENTED
Coverage, backing, pool, and settlement arithmetic
RCR, B_SEA, G_pool, S_cap, and payout caps exist in code.
PROVEN
Payout never exceeds settlement capacity
P_final is defined as min(L_settle, S_cap).
SPECIFIED
Canonical E_reserve derivation
The QSA-resident integral is doctrine, not yet implemented in the audited measurement chain.
OPEN
Independent third-party replay
The deterministic audit mechanism exists, but no external verifier has published agreement or disagreement.
OPEN
Operational, counterparty, and cyber risk domains
These institutional risk categories are not yet represented in the coded five-domain taxonomy.
Source anchors
  • valued_packet.rs:229-253
  • Canonical Reserve Doctrine, Chapters 9 and 11
  • qsa/web/components/qsa-dashboard/tabs/Sea.tsx
  • REPLAY_BASELINE_v1

Based on The Canonical Reserve Doctrine, Version 1.0, verified against repository state as of July 7, 2026. Claims must be re-verified before their status is upgraded.