State transition model

Phase I — Ingest · Entropy

The kernel ingests untrusted observations from the edge — sensors, machines, oracles, human operators. Events exist only as signed claims; truth has not yet been established.

• Origin signature is recorded but not yet attested.
• Claims are addressable but not yet composable.
• The kernel emits CLAIM_RECEIVED — observers can listen, liquidity cannot move.

Phase II — Consensus · Trust

An event advances only when it is cryptographically proven real, and every actor and asset has been verified for identity, jurisdiction, compliance, solvency, and ownership.

The verification round-trip is sub-second on mainnet — median proof finality lands at 1.18s across 184 active verifiers and 33 jurisdictions.

Phase III — Execute · Finality

On verification, the kernel emits STATE_VERIFIED and atomically triggers irreversible settlement. Capital releases in the same block. No verified-but-unsettled state exists.

1// the lifecycle of a single event
2{
3  schema:   "trade.delivery.v1",
4  state:    "STATE_VERIFIED",       // CLAIM_RECEIVED → PROOF_ADVANCED → STATE_VERIFIED
5  proof: {
6    hash:   "0xA1F4·8B2E·9F11·4C7A",
7    block:  4128902,
8    epoch:  2,
9    ttf_ms: 1184,                   // time-to-finality from claim received
10  },
11  attest: {
12    id:        "RISA·trade",
13    standard:  "ISO/IEC 17025",
14    signature: "<detached>",
15  },
16  payload: { /* schema-typed, signed at origin */ },
17}

Finality guarantees

• Exactly-once delivery per event.proof.hash.
• Atomic settlement in the same block as verification.
• No rollbacks — once STATE_VERIFIED fires, the underlying ledger entry is immutable.
• Public auditability via XRPL — every event is addressable on a public explorer.