Solutions

Resources

Solutions

Resources

Changelog
22 June 2026ComplianceArchitecture

Two jurisdictions, one rules engine

MiFID II and CVM/ANBIMA in the same deterministic engine, and why a compliance outcome is not a probability.

Compliance is the one place we refuse to let a model decide. This release put MiFID II and Brazil's CVM and ANBIMA rules into the same deterministic engine. Give it the same client, mandate and instrument and it returns the same verdict every time, with the rule it applied written next to the answer.

A large language model can draft, summarise and explain. It does not get a vote on whether something is suitable, because a compliance outcome is not a probability and no regulator will accept "the model was fairly confident."

One engine, two rulebooks, and room for the next, because the jurisdictions a European wealth manager touches only multiply. The reasoning is legible on purpose. That is the whole point of doing it this way.