Validator → Executor → Hook.
OMA runs inside the institution’s own trust boundary: policy, execution, and evidence as three composable modules on a per-mandate smart account, fed by the off-chain judgment core, executing against protocol rails including STN.
Three modules. One mandate check.
Mandates are compiled, not filed.
01// compiled by PCE · pinned on the account02{03 policyCommit: "0x9f4a…",04 rule: {05 id: "single_issuer_pct",06 source: "IMA §4.2 · exposure ≤ 8.0%",07 cap: 8.0,08 },09 verdict: {10 intent: "SELL 12K UNITS · SCX-T",11 result: "ESCALATE",12 reason: "post-trade 8.4% vs cap 8.0%",13 },14}
The PCE compiles the mandate and the applicable regulation into a typed, versioned, counsel-attested policy bundle, pinned to the account by its commit hash. The Validator evaluates every leg against it before settlement, deterministically.
Verdicts carry rule IDs and reasons. Rejections are blocked outright; soft-band breaches escalate to a named officer whose override, with its rationale, becomes part of the record. Same policy hash, same intent, same verdict: an auditor can replay any decision, forever.
Join the waitlist for access testing.
Access is rolling out to a scoped cohort of regulated institutions through structured, milestone-gated pilots. Drop your details and we'll coordinate briefings, mandate intake, and pilot onboarding as your category opens.