§ 01 / Architecture
One account. Every mandate, enforced.
fig.02 / oma architecturesovereign · modular · verifiable
§ 02 / Modules
Composable by construction.
MODULE · 01
Policy Management (PaaS)
Codify mandates, risk limits, and execution policy once. Signed, versioned, and enforced per-order.
MODULE · 02
Automated Trade Mgmt (ATM)
Routing, sizing, and rebalancing across venues under institutional mandate.
MODULE · 03
Attestation Layer
Every action produces a verifiable on-chain receipt. Audit without reconciliation.
§ 03 / Policy-as-code
Mandates are code, not PDFs.
mandate.ts · excerptmandate.ts
01export const mandate = {02 id: "MANDATE_V4",03 scope: ["tokenized_funds", "rwa"],04 limits: {05 max_notional_usd: 50_000_000,06 max_daily_turnover_bps: 800,07 max_venue_concentration: 0.35,08 },09 best_ex: { surface: "stn", leak: "off" },10 attest: { on: "every_order" },11};
OMA treats institutional mandates the way regulated code treats infrastructure: declarative, versioned, signed, and enforced at the protocol boundary.
Every order is evaluated against the live mandate before it reaches any venue. Violations are rejected deterministically. No flags, no human reconciler.
KEY PROPERTY
If it isn’t in the mandate, it doesn’t execute. Full stop.
§ 06 / Access testing
Join the waitlist for access testing.
Early access is rolling out to a small cohort of institutions. Drop your details and we'll coordinate briefings and pilot onboarding as your category opens.