SURFACE · 01 / PCE · OFF-CHAIN

Policy Compilation Engine.

The authoring surface of the judgment core. The PCE compiles public regulatory corpora and a fund's private mandate into a typed, versioned, source-pinned policy bundle: machine-checkable rules the OMA enforces before execution. Each compile emits a policyCommit hash, the first link of the binding chain.

pce · compile runlive
corpusMiCA · MiFID II · IMA
bundlev2026.06.0
rules_approved142
flagged_to_counsel11
extractions_rejected3
policy_commit0x9f4a… · PINNED

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.

fig.05 / pce pipelineextract → review → compile → sign & pin
SOURCE TEXTMiCA · MiFID IIDLT PILOT · RTSIMA · MANDATEPROSPECTUS · ISDAPUBLIC CORPUS +PRIVATE TERMSPCE · OFF-CHAIN · PROPRIETARYPolicy Compilation EngineEXTRACT · GLASS-BOXLLM reads source text → typed measures onlyREVIEW · COUNSEL IN THE LOOPflagged clauses confirmed, corrected, or rejectedCOMPILE · TYPED DSLpolicy-as-code bundle · deterministic evaluationSIGN & PINpolicyCommit = hash( bundle ) · pinned on the OMA01 / AI IN EXACTLY ONE PLACE · EVERYTHING AFTER IS DETERMINISTICOUTPUTSSIGNED BUNDLE → OMApolicyCommit → CHAINEXTRACTION TRACESVERSION HISTORYEVERY CORRECTION ISA LABELLED TRACEFIG 05 · PCE · FROM PROSE TO policyCommit

Constrained where it must be. Deterministic everywhere else.

GUARANTEE · 01
Glass-Box Extraction
AI operates in exactly one place: reading source text into a typed schema under constrained generation. Everything after extraction is deterministic: compiled, versioned, replayable.
GUARANTEE · 02
Counsel in the Loop
Every uncertain clause routes to counsel before it enters a bundle. Each confirmation, correction, or rejection is recorded as a labelled extraction trace; these traces are the first entries in the mandate's record.
GUARANTEE · 03
Source-Pinned Provenance
Every predicate is verified programmatically, not by another model, against schema invariants and source-text overlap, and carries span-level provenance back to the clause and the reviewer.

The first link.

compiled rule · excerptbundle.json
01// bundle v2026.06.0 · rule 87 of 142
02{
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}
09
10// → 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.

KEY PROPERTY
The rule that was authored is provably the rule that executes. Same bundle, same intent, same verdict, forever.
§ 06 / Access Testing

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.

§ JOIN WAITLIST · ACCESS TESTING
< 60 SEC
◦ INSTITUTIONAL EMAIL REQUIRED · PERSONAL ADDRESSES NOT ACCEPTED
CONFIDENTIAL · NO SPAM · CATEGORY-ORDERED ROLLOUT