From prose to policyCommit.
Regulation and mandate go in as documents; what comes out is a signed bundle of typed rules a machine can enforce and an auditor can trace back to the exact clause. The typed DSL is the human-facing front end; a policy-as-code engine is the evaluation backend.
Constrained where it must be. Deterministic everywhere else.
The first link.
01// bundle v2026.06.0 · rule 87 of 14202{03 measure: "single_issuer_pct",04 source: "IMA §4.2 · single-issuer exposure ≤ 8.0%",05 threshold: 8.0,06 band: { soft: true, authority: "risk_officer" },07 attestation: { reviewer: "counsel", status: "APPROVED" },08}0910// → policyCommit = hash( bundle ) · 0x9f4a…
The policyCommit is pinned on the institution’s OMA at onboarding and rebuilt on every mandate amendment. From then on, every downstream surface points back to it: the Validator’s decisionId, the AIA receipt, the STN match ticket, and the settlement evidence.
Jurisdiction rulepacks make the same rail enforce the correct rulebook per participant: an EU module first (MiCA, MiFID II product governance, AIFMD / UCITS depositary evidence), with Singapore and UAE following the launch footprint.
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.