How It Works

One event log. Every rail. Real-time.

The five operational primitives define who is in the system and where they operate. The three layers below define what happens to every event they generate — from architecture to finality to the controls that make it auditable.

Each page stands alone. Read in sequence if you are evaluating the architecture. Jump to Finality if the T+1 settlement monitoring question is the entry point. Jump to Security if the examination question is.

Architecture

Event-sourced core, instrument-agnostic position model, real-time data across every asset class — no overnight batch, no sub-ledger fragmentation.

Settlement & Finality

Deterministic, conditional, and probabilistic finality from the rail — DTC, SWIFT, Ethereum — not from message timestamps or settlement calendars.

Security & Controls

Maker-checker, WORM audit trail, and role-based access as structural properties of the event stream — not a compliance layer bolted on.