What Sovrient Is
Sovrient ingests measurements from calibrated sensor networks and applies a deterministic admissibility framework to produce sealed, replayable evidence. Name note: Sovrient is independent from and unaffiliated with Sovrin.
Governance Reconstruction Infrastructure
Reconstruct what the system saw, selected, and justified.
Sovrient turns independently observable signals into replayable evidence artifacts so teams can review machine-supported decisions without rebuilding the record from scratch.
View Mode
Executive view prioritizes plain-language sections. Switch to Technical for full protocol detail.
Start here if you need to know what Sovrient does, who it is for, and what can be independently checked before legal, technical, safety, or financial diligence goes deep.
Sovrient is not autonomy, a black-box score, or a settlement authority. It is the evidence-governance layer between raw machine output and accountable review, with replayable artifacts and declared scope boundaries.
Seismic is the live lane. Maritime AIS is published as a bounded governance seed over authoritative open U.S. coastal data; additional lanes, including cyber and public-record observatories, are introduced only when their verification surfaces are stable enough to publish. See the governance reconstruction surface for the current cross-lane posture.
Verify This Claim In 3 Steps
- Open measured event state for the current computed day.
- Check admissibility + gate state (DT0_STRICT pass/fail).
- Open sealed catalog and follow independent replay steps.
- Load machine state if you need a compact agent-readable entry point.
10Y BACKFILL: sync pending
REPLAY HASH: sync pending
BUNDLE HASH: sync pending
These anchors bind the audited interval. Verification is binary: hashes match or the verification check fails for that claim.
Backfill range is exact; “10Y” is a shorthand label for the audited interval.
Replay Hash binds deterministic recomputation of declared outputs under declared inputs.
Bundle Hash binds the sealed artifact set (manifests, leaves, signatures) as published.
PROTOCOLSOVOS_CANON_V1
ATTESTATION CLASSVOSINT (Verifiable Open-Source Intelligence)
EVIDENCE MODELMerkle-sealed, deterministically replayable
FAILURE SEMANTICSFail-closed — unverifiable data does not pass
WITNESSINGEd25519 signature (detached, GPG-format) + TSA timestamp
ACTIVE LANESeismic catastrophe risk
LATEST COMPUTEDsync pending
ANCHOR STATUSHistorical Sepolia anchors active; latest computed day may be pending on-chain publication.
STATUS KEYARTIFACT_FINAL = off-chain sealed evidence valid · ANCHOR_PENDING = on-chain publication not yet confirmed
PROTOCOL v1.0 · SCHEMA v2.4 · ATTESTATION FORMAT v1.1 · CI-1 (Catastrophe Infrastructure Lane)
Version labels may evolve; sealed artifacts are final once signed and hashed.
Fail-closed: any missing or failed artifact => gate=HOLD/FAIL; no downstream admissibility.
Deterministic replay: the same declared inputs, command, model/version, and canonical serialization produce identical outputs and hashes.
Live Credibility Snapshot
Active Lane
Seismic catastrophe risk
Backfill
-- days
Replay Hash
sync pending
Bundle Hash
sync pending
Artifact State
ARTIFACT_FINAL (off-chain)
Anchor State
Historical active · latest pending
Client Feed
Sealed Catalog V1 · deterministic · hash-anchored
Backfill Coverage
--Days
Trigger Days
--
M4+ Events (Latest Day)
--Events
Sources
--Networks
Counts reflect live attestation status at time of page generation.
What Happened
Latest computed event summary will appear here.
How Verified
Verification roots and custody context will appear here.
Status
Official versus provisional state will appear here.
60-Second Overview
Start Here Before the Protocol Detail
Sovrient publishes sealed, replayable event measurements. Independent networks must agree. Computation is deterministic. Evidence is cryptographically witnessed.
- Corroborate independent source observations within declared tolerances.
- Compute deterministic measurement outputs from declared inputs and environmental bounds.
- Seal artifacts with signatures, hashes, and timestamp witnesses.
What you get: a bundle any counterparty can independently verify. What it is not: settlement authority, underwriting advice, or legal adjudication.
Plain-Language Terms
DT0: declared totals reconcile with zero residual under declared rounding, ordering, and witness rules.
Data → Seal → Drift lane: raw ingestion evidence is hashed, measured, and sealed before downstream interpretation.
Ground-up loss estimate from deterministic model execution; objective evidence input, not a settlement determination by itself.
Verifiable open-source intelligence: public-source data upgraded to evidentiary grade through corroboration, determinism, and cryptographic witnessing.
What It Is Not
- Not a settlement determination authority
- Not underwriting advice or valuation output
- Not legal adjudication
Why It Matters
- Reduces single-source dependency
- Supports faster audit and review
- Moves disputes from narrative to replay checks
Verify In 3 Steps
- Open the latest attestation bundle
- Recompute hashes from published artifacts
- Confirm anchor and signature references
Who This Is For
- Risk and structuring teams
- Claims and operations leads
- Legal, compliance, and audit reviewers
Faster Audit CyclesReplay checks are deterministic, so reviewers validate invariant outputs instead of rebuilding narrative context.
Lower Dispute FrictionReduces dispute surface by converting arguments into replay checks.
Clear Role SeparationSovrient publishes pre-settlement measurement evidence; authorized counterparties retain settlement authority.
Operational ResilienceFail-closed gating prevents unverifiable inputs from entering financial calculations.
Problem Statement
The Oracle Problem Isn't About
Data Availability. It's About
Evidentiary Admissibility.
When billions move on a single measurement, the question is not whether the data is available — it is whether the data is provably consistent, replayable, and non-manipulated under declared scope. OSINT-grade data is being used in settlement-grade systems. That gap is structural, not ideological.
Historical precedent matters: FONDEN-era trigger disputes showed how post-publication source revisions can move capital when evidentiary controls are weak.
Correctness is defined relative to declared inputs and tolerances.
01
Single Point of Failure
Parametric triggers often rely on a single data source. If that source is wrong, manipulated, or delayed — the entire contract fails. Any system that moves money based on OSINT is structurally unsafe.
SOVRIENT ANSWER
Latest corroborated day state is being synchronized from sealed artifacts.
02
No Reproducibility
Can you replay the computation that determined a payout? Can you verify the data hasn't been modified since measurement? If the answer is no, you don't have evidence — you have narrative.
SOVRIENT ANSWER
Replay hash sync pending is identical across independent runs. -- days, -- trigger days, zero computational variance (DT0) under declared scope. Same input → same output → same hash.
03
Trust Without Evidence
Traditional oracles rely on institutional trust. Settlement-grade systems require cryptographic proof — independently verifiable, deterministically replayable, and non-repudiable.
SOVRIENT ANSWER
Every attestation is Ed25519 signed, SHA-256 sealed, with quantified corroboration metrics — sync pending (latest sealed day) — preserved as contemporaneous evidence before the financial calculation executes.
Verified Open-Source Intelligence
From OSINT to VOSINT
Evidentiary-grade, open-source intelligence whose integrity, provenance, timing, and completeness are cryptographically attested, independently corroborated, and deterministically reproducible — designed to support verification and governance workflows under contract-defined authority.
OSINT classifies access.
VOSINT classifies admissibility.
VOSINT classifies admissibility.
VOSINT =
Corroboration
+
Computational Determinism
+
Cryptographic Witnessing
OSINT — Informational
- Publicly available, anyone can scrape
- Single source, unverified
- Manual reconciliation
- No tamper evidence
- Unreproducible analysis
- Verification is social or reputational
OSINT informs humans.
VOSINT — Attestation-Grade
- Multi-source corroborated
- Cryptographic provenance (hashes, signatures, Merkle roots)
- Computationally deterministic replay engine
- Independent recompute by any party; consensus policy is optional and contract-governed
- Bit-for-bit reproducible
- Fail-closed: unverifiable data does not pass
- Anyone can independently recompute under declared scope and model/version
VOSINT authorizes systems.
Why the "V" Earns Its Keep
Three properties. Non-overlapping. Each independently necessary.
V₁
Verified
The data passed explicit integrity checks at the time of ingestion. Not "seems right" — mechanically verified.
V₂
Verifiable
Any third party can independently recompute and confirm the same result under declared scope, command, and model/version. Verification is deterministic, not reputational.
V₃
Witnessed
The data's existence, state, and timing were independently attested — non-repudiable. Merkle seals and TSA timestamps are not version control. They are witnesses.
Open Sources, Verified
The Sovrient protocol ingests from the same public authorities available to all participants — USGS, EMSC, JMA, GFZ, IRIS. The distinction: every observation is hashed at fetch time, corroborated across sources, and sealed with cryptographic proof.
Open Standards, Auditable
Loss calculations use Oasis LMF (open source, industry standard). Vulnerability curves are published CSV files. Cryptography uses Ed25519 (detached, GPG-format), SHA-256, and timestamp witnessing. No proprietary component is required for the published verification path.
Corroboration Evidence
Quantified Agreement.
Sealed Before Calculation.
Before any loss calculation runs, independent seismological networks must agree within tolerance. The corroboration record — showing exactly how close sources agreed on location, magnitude, and timing — is sealed as a cryptographic artifact. This is not metadata. It is forensic-grade input verification, preserved as contemporaneous evidence.
Important distinction: The ±60s / ±50km / ±0.2M tolerances are post-event agreement thresholds between independent observation networks — not prediction intervals. This system verifies what already happened. It does not forecast what will happen. "Deterministic" refers to the computation (same inputs → same outputs → same hash), not to the seismology.
Spatial Agreement
--km
EMSC ↔ USGS epicenter distance
Temporal Agreement
--sec
Origin time difference
Magnitude Drift
--Δmag
Independent measurement agreement
Latest Daily GUL
$19,799,793.76
Latest day metrics sync pending.
GUL shown here is a deterministic loss proxy under declared contract parameters, not a final claims settlement amount.
Evidence Role: Pre-Settlement Evidentiary Layer (Sealed Physical Evidence, Replayable)
This ground-up loss figure is an objective, replayable physical loss estimate sealed shortly after the event. Sovrient applies incentive-orthogonal corroboration (IOC): agreement across disclosed source classes with non-aligned publication incentives under the declared dependency model. It provides a pre-settlement evidentiary layer for deterministic measurement and threshold evaluation. It does not make settlement determinations; final determination remains with authorized contract parties.
Narrative Endpoint
DSD Proof Lane (Operational)
SYNC PENDING
RAG SYNC PENDING
Raw bytes and capture-window metadata are sealed before interpretation. Later source revisions produce new attestations and do not overwrite first-capture evidence. This lane is a pre-settlement evidentiary layer for deterministic measurement and threshold evaluation; final determination remains with authorized contract parties.
DateN/A
Seismic DriftN/A
PMU TVE MaxN/A
Pre-Seal HealthN/A
Replay HashN/A
SourceN/A
LaneN/A
RAG DriversN/A
Event: ms_t5903010 | 2026-02-12
Chile (Coquimbo Offshore) · M6.2CONFIRMED ✓
🇪🇺
EMSC (Europe)
30.8012°S, 71.4451°WM6.2
2026-02-12T13:34:30.730Z
Corroboration Record (Sealed Pre-GUL)
SPATIAL DELTA
0.000 km
Within ±50km tolerance
TEMPORAL DELTA
0.384 sec
Within ±60s tolerance
MAGNITUDE DELTA
0.000
Within ±0.2 tolerance
Event: ms_t5901840 | 2026-02-08
45 km SSW of Maisí, Cuba · M5.5T+40min LIVE CAPTURE ✓
🇪🇺
EMSC (Europe)
19.8899°N, 74.3710°WM5.5
2026-02-08T12:00:09.030Z
🇩🇪
GFZ (Germany)
19.9060°N, 74.3370°Wmb 5.74
2026-02-08T12:00:09.780Z
Retrieved via manual curl · FDSN endpoint reset during automated fetch
Live Corroboration · Sealed Feb 8, 2026 12:38 UTC
SPATIAL DELTA
0.000 km
EMSC ↔ USGS identical coordinates
TEMPORAL DELTA
0.000 sec
EMSC ↔ USGS identical timestamp
MAGNITUDE DELTA
0.000
Both Mw 5.5 · GFZ: mb 5.74 (body-wave scale)
Notification-to-Attestation Timeline
T+0M5.5 earthquake strikes 45km SSW of Maisí, Cuba · 10km depth · 12:00:09 UTC
T+15minPush notification received via earthquake monitoring app
T+20minDNS failure resolved · ms_fetch_day.py initiated
T+22minGFZ FDSN connection reset detected → system fail-closed (§7) → no partial output published
T+24min4-source ingest complete (USGS + EMSC + IRIS + JMA) · GFZ failure recorded in manifest
T+25minms_corroborate_day.py → 34 observations → 8 confirmed events · Cuba: CONFIRMED
T+28minms_gul_from_corroboration.py → Oasis LMF run complete: $19,799,793.76 (1,782 unique areaperils)
T+38minms_gul_receipt.py + ms_gul_attestation.py → Ed25519 sealed
T+40minFull attestation bundle: corroboration + GUL + signature · Hash: 6220194702…
How This Answers All Three Problems
P1Single Point of Failure Exposure → Reduced. Single-source events (
SINGLE_SOURCE) are excluded from GUL. If only one network reports an event, it does not enter the financial calculation — regardless of magnitude. 10-year backfill identified $5,300,000.00 in false payouts that corroboration would likely have prevented under these declared rules.P2No Reproducibility → Addressed. The corroboration record is deterministic. Same inputs, same tolerance parameters, same matching algorithm → same confirmed/rejected classification. The replay hash
sync pending is identical across independent runs. -- days. Zero computational variance (DT0) under declared scope.P3Trust Without Evidence → Reduced. Quantified agreement metrics (km, sec, Δmag) are preserved as sealed artifacts — not just a pass/fail flag. The corroboration record is Ed25519 signed and SHA-256 hashed before any loss calculation runs. The evidence exists before downstream dispute processes begin.
The corroboration artifact is the evidentiary boundary. GMPE methods are public, while daily sealed incentive-orthogonal corroboration (IOC) metrics are not typically published as replayable attestation artifacts.
Method
Three Problems.
Three Answers.
Each problem identified above has a direct, operational answer — not a whitepaper promise, but a live system producing verifiable outputs daily. The Sovrient protocol reduces reliance on institutional trust by making verification computable.
ANSWERS PROBLEM 01
Multi-Source Corroboration
Five independent seismological networks (USGS, EMSC, JMA, GFZ, IRIS) must agree within defined tolerance before an event is confirmed. Disagreements are surfaced, not suppressed. Single-source events are excluded — they never enter the financial calculation.
Live: Feb 12 — Chile M6.2 corroborated across EMSC + USGS with zero spatial drift and sub-second temporal agreement
ANSWERS PROBLEM 02
Deterministic Computation
Every calculation produces identical results across execution paths. Not approximately reproducible — identical, bit-for-bit, across substrates. Run the pipeline twice, compare the hash. Match or fail. No ambiguity.
Live: -- days · replay hash identical across runs
ANSWERS PROBLEM 03
Cryptographic Finality
Every attestation is timestamped, hashed with SHA-256, signed with Ed25519. Corroboration metrics are sealed as artifacts before loss calculation begins. The proof exists before anyone has a reason to dispute it.
Live: attestation_ms_gul_sync_pending.json · Ed25519 sealed at T+40min
Scope Declaration
What This System Does.
What It Does Not.
Settlement-grade systems require explicit boundaries. The following declarations define the scope and limits of the Sovrient verification protocol.
Within Scope
Measurement attestation — cryptographic proof that a physical event was observed, corroborated, and sealed
Multi-source corroboration across independent seismological networks
Deterministic loss estimation using published, open-source models (Oasis LMF)
Cryptographic witnessing — hash, signature, timestamp, on-chain anchor
Replay verification — any party may recompute and confirm identical output
Explicitly Out of Scope
Valuation — this system provides measurement attestations, not asset pricing
Adjudication — the protocol publishes admissible evidence; it does not adjudicate claims
Prediction — no forward-looking statements of any kind; tolerances (±60s, ±50km, ±0.2M) are post-event observation agreement thresholds, not forecasting intervals; attestations reflect observed, past-tense events only
Replacement of actuarial judgment — this is an evidentiary layer, not a substitute for professional assessment
Source certification — the protocol attests cross-source consistency under declared tolerances; it does not certify any individual provider's absolute accuracy
Independent Verification Procedure
01Obtain the attestation bundle by
BUNDLE HASH02Verify the Ed25519 signature (detached, GPG-format) against the published fingerprint
03Recompute SHA‑256 for each leaf and rebuild the Merkle tree
04Compare the recomputed root to the published
RANGE MERKLE ROOT05If an on‑chain anchor exists, verify the root on the designated ledger; otherwise status remains AWAITING ON-CHAIN WITNESS
06If any step fails, the attestation is invalid for protocol publication. No partial verification is accepted for protocol publication.
Verification failure is binary. There is no degraded mode.
This procedure is executable using the published verifier kit; no privileged access is required. If it cannot be completed independently, the attestation is not witnessed.
Replay execution is defined over the published command, model version, seed, and dataset hashes; environmental variance outside these bounds (hardware, OS, filesystem ordering) is out of scope. All bundle components are ordered deterministically prior to hashing — canonical ordering ensures identical Merkle roots regardless of reconstruction path.
Verifier Kit
STATUS: PUBLISHED · Bundle format and verifier scripts are active for independently replayable checks.
What DMSS Replaces
Single-source trigger authority with no corroboration requirement
Non-replayable settlement computations accepted on institutional trust
Magnitude-only parametric triggers that cannot account for spatial exposure
Narrative-based dispute resolution where evidence is reconstructed after the fact
⚠ What DMSS Does Not Replace
Catastrophe models — DMSS is an evidentiary layer, not a modeling engine
Actuarial judgment — professional assessment remains outside protocol scope
Claims adjustment — the protocol attests measurements, not claim validity
Regulatory authority — DMSS produces evidence; regulators interpret it
Autonomous Decisioning
From Corroboration
to Settlement
The verification pipeline does not terminate at measurement. Multi-source corroboration (P1) feeds deterministic loss calculation (P2), producing cryptographically sealed attestations (P3) — every step signed and replayable. The chain from raw seismological observation to financial attestation is unbroken.
Firm Simulation — 10Y Backfill Run
CLEAN RUN ✓
Coverage
sync pending
Backfill
-- days
Trigger Days
--
Risk Limits
5% daily / 29% cum.
| Metric | Value | Notes |
|---|---|---|
| Total Ground-Up | $18,604,182,501.17 | Raw modeled loss (Oasis LMF) |
| Layer Loss | $1,260,894,998.98 | Parametric index triggers |
| Latest Day (sync pending) | -- | sync pending |
| Invalid Days | 0 | ✅ Invalid Days: 0 (no fail-closed publication events across the audited interval) |
Live Attestations
Live Attestations
Corroboration results from the incentive-orthogonal corroboration (IOC) pipeline. Each row represents a cryptographically sealed daily attestation.
Source of truth: live counters and ticker metrics are derived from
data/ms_zones_latest.json, data/dsd_latest.json, data/dsd_release_state.json, data/rinex_witness_latest.json, and sovrient-live-metrics.js. Sealed artifacts are authoritative when values differ.Executive Summary
Latest status is visible in the hero metrics and ticker. Full attestation tables, Merkle traces, and deployment anchors are available in Technical mode.
KEV Observatory
Compact operator summary for the KEV observation lane. Full trend and term detail live on the status surface.
KEV Date
Loading...
Gate State
Loading...
Source Hash Changed
Loading...
Broad Matched
Loading...
Asset Matched
Loading...
Trend Window
Loading...
Loading KEV interpretation...
Canonical Metrics Snapshot
M1Backfill interval
sync pending · -- days · Trigger days --. Backfill day count is the number of sealed daily attestation records in the audited set (not raw calendar-day delta).M2Latest computed attestation day
sync pending · Replay hash sync pending.M3Live compute status and anchor publication status are separate controls: computation can be complete while latest-day anchor publication is pending.
DateSourcesConfirmedGULAttestation Hash
sync pending------sync pending
2026-02-0745$4,113,998.79f2e3452aa7…
2026-02-11830$11,883,996.433f9003353e…
2026-02-0348$9,855,997.128116da1ce4…
2026-02-0246$4,533,998.69e25f0af3a1…
2026-02-0148$10,657,996.786c54a07866…
2026-01-31411$11,661,296.5680f9d4052e…
RANGE MERKLE ROOT: b85fed30a11e9c21e6609bfadf48fdb78c9656dabf2d7b93f985587f5186cb82
SIGNING KEY FPR: Ed25519 56FA491FF6EA4FE5E86D21A775867DAF1EE06FC4
SIGNING KEY FPR: Ed25519 56FA491FF6EA4FE5E86D21A775867DAF1EE06FC4
On-Chain Deployment Anchors
Network
Type
Address / Tx
Status
Historical daily attestations are anchored on Sepolia. Latest computed attestation day:
sync pending. Anchor publication can lag computation; use the “Latest Daily Tx” row as the authoritative on-chain reference for the latest anchored state. Historical intraday anchor: 0x0b79...ef5d.
Technical Architecture
Verification Pipeline
From raw seismological data to cryptographically sealed attestation. OSINT enters; VOSINT exits.
Data Sources
Independent Networks
The same public authorities available to all participants. Distinction: every fetch is hashed and corroborated.
- USGSUSA
- EMSCEU
- JMAJP
- GFZDE
- IRISNET
Corroboration
Consensus Engine
Deterministic matching across sources. Disagreements are surfaced, not hidden.
- Time tolerance±60s
- Distance tolerance±50km
- Magnitude tolerance±0.2
Output: CONFIRMED / DISPUTED / SINGLE-SRC
Tolerances are post-event observation agreement thresholds, not prediction intervals.
Attestation
Merkle + Seal
Evidence is hashed, signed, timestamped, and eligible for anchoring. Witness state is declared in Deployment Anchors.
- SHA-256Hash
- Ed25519 (detached, GPG-format)Sign
- TSATime
- On-chain anchorSepolia
Determinism: same inputs → same artifacts → same hashes. (bit-for-bit reproducible)
Fail-closed: unverifiable data does not pass. OSINT enters; VOSINT exits.
SOVOS_CANON_V1 · Schema v2.4
Fail-closed: unverifiable data does not pass. OSINT enters; VOSINT exits.
SOVOS_CANON_V1 · Schema v2.4
Backfill Proof: 10Y run is bound by replay hash and bundle hash.
Witnessed: every attestation is independently attested, non-repudiable, and contemporaneous.
Witnessed: every attestation is independently attested, non-repudiable, and contemporaneous.
Parametric Settlement Standard
Current Treaty Language
Is Not Built for This Depth.
Catastrophe bond offering circulars typically specify a trigger in a few pages: one data source, one parameter, one institution's word. The treaty commonly does not address what happens when sources disagree, when magnitudes are revised post-publication, or when a moderate earthquake in a dense exposure zone produces more loss than a larger event in open ocean. The evidentiary standard has not kept pace with settlement automation.
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.
For Institutions
Institutional Interfaces
The Sovrient protocol delivers VOSINT-grade, evidence-bound loss proxies for daily oversight — complementary to, not a substitute for, traditional claims and actuarial accounting. The system provides LPs and risk committees a deterministic, auditable signal between event and official loss release, without altering how final settlements are calculated. Attestation-grade intelligence for systems that require admissibility, not availability.
Attestation Delivery: From Hash Chain to Human-Readable Instrument
Every attestation exists in two layers. The cryptographic layer — Ed25519 signatures, SHA-256 hashes, Merkle roots — is the source of truth, independently verifiable by any technical party. The PDF rendering is the presentation layer: a human-readable document designed for risk committees, legal review, deal rooms, and treaty addenda. The PDF does not replace the hash chain. It references it — every claim in the document is anchored to a specific hash that can be independently verified.
01Cryptographic attestation is generated. Corroboration record sealed → GUL computation runs with hashed inputs → output hash recorded → Ed25519 signature binds the bundle → timestamp recorded. This is the evidentiary root.
02PDF attestation is rendered. The sealed bundle is rendered as a structured, human-readable document containing: corroboration metrics with source attribution, per-event loss decomposition with areaperil cell counts, input/output hashes in full, signature fingerprint, and independent verification procedure. Designed for institutional circulation — printable, attachable, archivable.
03Recipient verifies at their chosen depth. A risk committee reads the PDF as a summary. A technical auditor extracts the hashes and replays the computation. A legal team references the document in a treaty addendum. All three are reading the same attestation at different layers of abstraction — and any of them can escalate to full cryptographic verification at any time.
The PDF is a human-readable rendering; the signed hash chain is authoritative.
A report summarizes conclusions. This rendering references cryptographic anchors that allow independent hash-based verification under declared scope.
AI/ML Integration Pattern (Public-Safe)
Sovrient is designed to operate as a deterministic evidence layer alongside third-party AI/ML underwriting and risk systems. Pricing and model interpretation remain with the model operator; Sovrient contributes replayable measurement evidence for downstream governance and verification. Example: the Chile M6.2 record (
t5903010) was corroborated and sealed before loss computation, then replayable for downstream model governance.01Modeling remains predictive. Third-party AI/ML systems perform underwriting, pricing, and portfolio decisions under their own governance.
02Evidence becomes deterministic. Sovrient publishes corroborated, cryptographically sealed, replayable event-state measurements that can be independently verified.
03Technical dispute surface is reduced. Counterparties can validate declared measurement state through deterministic replay instead of narrative-only reconciliation.
Scope boundary: this layer is evidentiary only. It is not underwriting advice, not valuation output, and not legal adjudication. Canonical definitions: Section IV — Cross-Domain Geophysical Terms.
💼 For Intermediaries & PE
- Outside-in Stage 0 corroboration before full diligence spend
- Deterministic claim-to-evidence framing for high-cost deals
- Explicit unresolved-gap and contradiction mapping
- Reputation shield for narrative-heavy, evidence-light opportunities
- Institutional briefing material available on request
📊 For Cat Bond Managers
- Independent settlement verification based on live corroboration artifacts and declared tolerances
- Quantified corroboration metrics (km, sec, Δmag) sealed before loss calculation — contemporaneous evidence, not retroactive reconstruction
- Replayable computation — identical replay hash across independent runs, -- days verified
- Recent daily attestations are published in the live table and sealed catalog for direct inspection
- Fail-closed semantics: publication requires completed verification artifacts and declared exception handling
⛓️ For DeFi Protocols
- Attestation hashes compatible with on-chain verification
- Merkle inclusion proofs for settlement logic
- Witnessed timestamps + Ed25519 signatures
- Dispute-resistant evidence packs
- Fail-closed gating for execution safety
📈 For Cat-Bond ETF Sponsors
- Publishable verification packs for public markets
- Daily receipts and signed manifests
- Evidence lane without exposure to private IP
- Hash handles for transparent disclosures
- Independent verification procedure included
🧠 For Cat Modelers
- Audit overlay: input/output hash chain
- Replayable run certificates without IP leakage
- Deterministic receipts for compliance
- Proof that stated inputs produced stated outputs
- Optional on-chain anchor compatibility
🌦️ For Parametric Insurers
- Multi-source trigger corroboration
- Witnessed event evidence for disputes
- Deterministic loss proxies
- Signed bundles suitable for adjudication
- Fail-closed verification procedure
🔗 For On-Chain Re Protocols
- Attestation roots compatible with smart contracts
- Merkle inclusion proofs for settlement
- Non-repudiable signatures and timestamps
- Chain-agnostic anchor policy (testnet → mainnet)
- Fail-closed semantics for execution safety
🗃️ For Data Markets & Oracles
- Signed range packs with provenance
- Deterministic transforms for auditability
- Chain-of-custody verification steps
- Hash handles for downstream distribution
- Independent reproducibility without coordination
🚢 For Maritime Autonomy & Port Systems
- Governed maritime track evidence from authoritative open U.S. coastal AIS
- Real Hampton Roads source slice with manifest, hashes, and bounded replay posture
- Explicit coverage-limit disclosure: not live, not global, not a fleet-scale anomaly claim
- MAS adapter seam already defined for evidence packaging and downstream governance
- Useful when admissibility, provenance, and replay matter more than another live vessel map
🛡️ For Government & Prime Teams
- NAICS 541690-aligned evidence engineering and governance reconstruction posture
- Replayable public proof surfaces for maritime AIS, machine-state discovery, and bounded review workflows
- Useful as the adjudication and evidence layer above sensing, autonomy, and mission software
- Prime-safe positioning: not a replacement for collection networks or operational systems
- Dedicated capabilities surface for contracting and teaming review
Contact Sovrient
Use this intake for diligence screens, verifier access, API mirror onboarding, intermediary conversations, maritime governance, cyber observability, government/prime teaming, or general institutional outreach.
Route yourself clearly. If you are coming from deal diligence, infrastructure, maritime/autonomy, cyber, real estate, public sector, contracting, prime integration, or data/oracle workflows, choose the closest audience and use case so the inquiry lands with the right lane owner.