01 · The Exchange

The Exchange

General Exchange's execution surface: tickets, routing, and evidence-bound checks so strategy intent becomes a controlled release—aligned to desk policy and limits before size touches the tape.

Open The Exchange

End-to-end platform topology

How orders, risk, compute, routing, and evidence connect through The Exchange—one direction of travel so auditors and desks share the same mental model.

Data flows from market feeds through normalization and risk fabric into GPU pools and smart routing, then to evidence ledgerFeedstick·OB·macroNormalizeschema·qualitylineage idsRisk fabricVaR·ES·scenariospre-trade gateCompute gridtokenized GPUtoken queueSORvenuesslippage ΔEvidence ledgerintent → fill → P&L hash chain

Signature workflow

Deterministic Risk-First Execution Loop

Every order is evaluated against live limits, scenario envelopes, and desk policies before release. Exposure is re-checked as fills update. Violations trigger automatic halts or approvals. The discipline mirrors internal systems used by BlackRock Aladdin and tier-one trading desks—adapted for tokenized compute and audit-ready evidence.

Four-step cycle from pre-release evaluation through exposure checks violations and desk discipline01Pre-releaseLimits · scenarios · policy map02ExposureLive net/gross · ladders03ViolationsHalts · maker-checker04DisciplineAladdin-grade control debt
  1. 01

    Pre-release evaluation

    Every order is evaluated against live limits, scenario envelopes, and desk policies before release.

  2. 02

    Continuous exposure checks

    Exposure is re-checked as fills update; state stays consistent with risk envelopes.

  3. 03

    Violations & halts

    Violations trigger automatic halts or approvals—no silent overrides.

  4. 04

    Desk-grade discipline

    Mirrors internal systems used by BlackRock Aladdin and tier-one trading desks.

Capability pillar

Execution & Routing Intelligence

SOR, slippage forensics, and live exposure in one loop.

How Execution & Routing Intelligence works on the platform
schematic
Smart order router choosing venues by liquidity cost and latency ellipsesSORplannerABCDslippage iso-cost

The router minimizes a cost surface: fees, impact, and latency—not just top-of-book snapshots.

Smart Order Router (SOR)

Venue selection optimized for liquidity, latency, and cost.

Slippage Attribution Engine

Break down slippage into market impact, timing, routing, and volatility.

Cost-Aware Execution Planner

Plan execution across compute cost, data cost, venue fees, and expected slippage.

Real-Time Exposure Dashboard

Live net/gross exposure, concentration, liquidity buckets, and breach escalation.

Capability pillar

Institutional Workflow & Evidence

Pre-trade gates, immutable ledgers, and policy-bound releases.

How Institutional Workflow & Evidence works on the platform
schematic
Immutable evidence chain from signal through fills to attributionSignalH1IntentH2OrderH3FillH4PnLH5Each hop appends signed metadata · second-line readable

Each hop hashes intent, child orders, and fills—building an evidence pack second line and regulators can traverse.

Pre-Trade Risk Gatekeeping

Validate constraints, liquidity, leverage, and exposure before orders are released.

Post-Trade Evidence Ledger

Immutable chain from signal → intent → order → fill → settlement → PnL attribution.

Desk Policy Enforcement

Maker-checker workflows, approvals, and parameter governance with role-based controls.

Model Lineage Tracking

Version control for models, datasets, compute environments, and deployments.

Capability pillar

Governance, Compliance & Controls

Attestations, exports, and policy-locked runtime.

How Governance, Compliance & Controls works on the platform
schematic
Policy gates attestation limits and role-bound deployment locksPolicylimitsattestexport

Controls are not PDFs—they are runtime gates that refuse to boot models or routes when limits drift.

Attestation & Limits Engine

Automatically enforce desk-level risk and compute-usage policies.

Audit-Ready Evidence Bundles

Exportable compliance packets for regulators, LPs, and internal audit.

Role-Bound Permissions

Segregation of duties for research, execution, approvals, and compute allocation.

Policy-Locked Deployments

Models can only run when bound to approved policy versions.