Current Treaty Practice
Single data source (typically USGS NEIC) as primary trigger authority (common practice)
Magnitude as primary trigger parameter — no spatial loss decomposition typically specified
No specification commonly included for source disagreement or post-publication revision handling
Calculation agent output accepted on institutional trust; computation is typically non-replayable
No reproducibility requirement commonly specified — independent verification not operationally feasible
Settlement disputes resolved through arbitration, not deterministic replay
Deterministic Multi-Source Settlement Standard (DMSS)
Implemented by Sovrient · Adoptable as a treaty addendum
DMSS is an optional treaty addendum template produced from Sovrient’s operating semantics.
DMSS formalizes Sovrient’s operating semantics into treaty language.
Trigger confirmation shall require ≥ 2 independent seismological networks agreeing within declared tolerances
Quantified corroboration metrics (km, sec, Δmag) shall be sealed as a cryptographic artifact before loss calculation executes
Loss computation shall use a declared, open-source model with spatially decomposed per-event, per-areaperil attribution
All computation inputs shall be individually hashed; execution must be deterministic and independently replayable
Settlement evidence bundle shall include Ed25519 signature, corroboration artifact, input hashes, and generation timestamp
Dispute surface reduced by deterministic replay and hash comparison; remaining legal or contractual disputes may proceed through arbitration
Worked Example: February 12, 2026 — Sealed Chile M6.2 Event Trace
A confirmed M6.2 event off Chile (token t5903010) was sealed with cross-source agreement before daily loss computation. Day totals were: 30 confirmed events, 12 GUL events, and $19,799,793.76 total GUL. The row below shows the primary corroboration and footprint evidence for this event from the sealed daily bundle.
| Event | Location | Mag | Cells | Sources | Spatial Δ | Temporal Δ |
| ms_t5903010 | Chile (Coquimbo Offshore) | M6.2 | 557 | EMSC + USGS | 0.000 km | 0.384 sec |
Cells = unique areaperil cells activated for this event in the sealed footprint set. Corroboration deltas are computed from the two-source confirmed bucket before loss computation. Daily total GUL for 2026-02-12: $19,799,793.76.
01Corroboration is sealed before financial computation. For the Chile M6.2 record, the EMSC and USGS reports converge at zero spatial drift and 0.384-second temporal drift inside declared tolerances. This event-state agreement is captured and hashed before any GUL computation executes.
02Cell-level footprint remains explicit and replayable. The event activated 557 unique areaperil cells in the sealed footprint set. Cell activation is part of the deterministic evidence chain, not an after-the-fact narrative.
03First-capture evidence remains immutable. Source bytes and capture-window metadata are sealed at publication. If providers revise parameters later, Sovrient issues a new attestation rather than mutating the original record.
04Daily context remains machine-verifiable. The same 2026-02-12 bundle reports 30 confirmed events, 12 GUL events, and $19,799,793.76 total GUL, with hashes published for replay and audit.
Numbers above are derived from the sealed 2026-02-12 bundle: corroboration artifact day_corroboration_2026-02-12.json, receipt day_receipt.json, deterministic GUL output gul_total.json (total_loss_usd 19799793.76), input hash input/footprint.bin: 3dbe9bf61160…, and Ed25519-signed attestation hash 95fda2ddd77d…. The computation is independently replayable; evidence is preserved before downstream dispute processes begin.
Draft Trigger Evidence Specification (DMSS)
For treaty addendum use. Terms are operational and verifiable. Defined tolerances are configurable per treaty; values shown are production defaults.
§1 CORROBORATION: A trigger event shall be deemed confirmed only when ≥ 2 independent seismological networks report consistent parameters within declared tolerances (default: ±50km spatial, ±60s temporal, ±0.2 magnitude). Single-source events shall not qualify for trigger confirmation regardless of magnitude. For purposes of this specification, independent networks are operated by distinct institutions with separate data collection, processing, and publication pipelines.
§2 SEALING ORDER: The corroboration record, including quantified agreement metrics (spatial distance, temporal delta, magnitude delta), shall be cryptographically sealed as a distinct artifact before any loss calculation executes. Input integrity shall precede financial computation.
§3 COMPUTATION: Loss calculation shall reference a versioned model identifier, declared vulnerability dataset hash, deterministic seed (if applicable), sample count, and execution command. All execution parameters shall be recorded as artifacts within the attestation bundle.
§4 ATTESTATION: The settlement evidence bundle shall include: corroboration artifact, individually hashed computation inputs, GUL output hash, Ed25519 signature, and ISO 8601 generation timestamp. The bundle constitutes the settlement proof of record.
§5 REPLAY: Any party to the treaty may independently replay the computation using the declared model version and hashed inputs. If independent replay produces a different output hash, the attestation should be treated as technical non-conformance pending contractual adjudication. Replay establishes computational facts; legal interpretation remains with the contracting parties and counsel.
§6 AUXILIARY WITNESSES: Attestations may incorporate GNSS ground displacement data (including NaVIC and QZSS constellation telemetry), NOAA consequence observation, Galileo system-state telemetry, and ARIA deformation-consistency evidence as additional corroboration modalities when available. Auxiliary witness data shall be sealed as separate artifacts within the evidence chain and are not required for trigger confirmation under this specification.
§7 FAILURE SEMANTICS: Fail-closed. If any verification step cannot be completed independently, the attestation is invalid for protocol publication. No partial verification shall be accepted. Any exception handling must be explicitly disclosed and contract-governed.
§8 MODEL VERSIONING: Loss computation shall reference an explicit, versioned model identifier and vulnerability dataset hash. Any change to model version, vulnerability curves, or execution parameters constitutes a new settlement regime and shall be explicitly declared to all parties prior to the effective date.
§9 EVENT CLOSURE: A Primary Event Attestation captures the mainshock once cross-network agreement stabilizes and before secondary seismic activity is incorporated. Aftershocks and subsequent events shall be attested separately and shall not retroactively modify the primary event record. Event closure is semantic (defined by cross-network corroboration convergence), not purely temporal. The closure boundary is protocol-defined and auditable.
§9 — Why Event Closure Matters
An earthquake is a clustered process: mainshock, coda, aftershocks. Settlement systems need to answer a specific question: what constitutes "the event" for trigger and payout purposes? Without a defined closure boundary, subsequent seismic activity can retroactively redefine the primary event — destroying determinism and creating dispute surface.
01Primary Event Attestation. Sealed at the point of maximum cross-network agreement, minimum semantic ambiguity. This is a single, bounded, deterministic object — one trigger-state record, one corroboration record, one sealed computation context. It is evidence counterparties may reference under contract.
02Secondary Seismic Activity. Aftershocks are attested as separate events with their own corroboration records. They may matter for damage accumulation, claims handling, or reinsurance exhaustion — but they do not edit the primary attestation. Related but non-identical.
03No retroactive mutation. Source parameter revisions after closure produce new attestations, not amendments. The original remains immutable, replayable, and valid for its defined scope. Later evidence extends the record — it does not overwrite it.
This gives parametric systems the closure they need and indemnity systems the continuity they need. The sealed Feb 12 Chile M6.2 record illustrates the same principle: event-state agreement is frozen for replay, and later revisions are published as new attestations rather than retroactive edits.
Adoption Path
01Parallel run. DMSS runs alongside the existing calculation agent for an agreed number of periods. Outputs are compared; no trigger authority changes during this phase.
02Non-binding overlay. DMSS attestation bundles are published as a verification pack alongside the official settlement. Parties may reference DMSS evidence in disputes but trigger authority remains with the incumbent agent.
03Escalation option. Treaties may optionally promote the DMSS attestation root to trigger authority after a successful parallel period, subject to agreement by all named parties.
Integration does not require replacing existing workflows. DMSS is designed as an additive evidentiary layer that strengthens settlement integrity without disrupting incumbent processes.