Evix works those cases to a documented outcome — one your MLRO can sign and a supervisor can verify without asking us.
synthetic company · demonstration file · every figure computed, none real
Your obligations do not come from one place. They come from FATF and industry practice, from the regulator where you are licensed, from the regulators and sanctions regimes your partners answer to, and from your own internal policies. Today that lives in twenty signed PDFs and in the heads of three people.
Evix reads those policies and assembles one requirements map — versioned, dated, and the same for every counterparty you assess. A counterparty closes it with facts from their own documents and registers, the way a puzzle closes. What is closed, what is still open, and what has been checked and cannot be established are three different things, and the map keeps them apart.
The assistant works twice. It reads your own policies — usually ten to twenty signed PDFs — and assembles them into the requirements map. Then it reads the counterparty's pack: 312 pages of apostilled documents in four languages, and it tells you what is in them.
A model is good at reading. It is not good at being cross-examined. So it extracts, proposes and drafts, and every stored fact carries the page, the character span and the quote it came from. Coverage is computed after that, by versioned deterministic rules, with no model in the path. Same map and same confirmed facts return the same answer today and in a year.
A trust in one jurisdiction, a nominee in another, a register with no obligation to answer. The case cannot be approved as it stands and there are no grounds to refuse it, so it sits. Every week it sits, it costs an analyst's attention and a merchant's patience.
Evix exists for that queue.
Evix does not replace the screening stack you already run. Identity checks, PEP and sanctions screening stay where they are, and their results enter the file as sources like any other.
What Evix takes is the queue that stack cannot finish — the multi-jurisdiction structures, the nominees, the registers that cannot lawfully answer. Route those cases here; everything else runs exactly as it runs today.
Beneficial ownership is usually the hardest element of the map to close, and it is where a case dies quietly.
Ownership is reconstructed edge by edge to the natural person. Each edge carries its percentage, the document or register it came from, and the date that source was current. Where the chain stops, it stops visibly — the node is a hollow in the surface, not an empty box somebody forgot to fill. Effective share is computed from the edges and marked as derived, never as verified.
An element of the map is closed by a fact, and a fact comes from somewhere — a register, a document, an issuer that will confirm. Our scope is 250+ registries, through our own connectors and partners. What matters for a case is not the count: it is what the register in front of you answers, what it does not, and what closes the requirement when it answers nothing.
Incorporation and the agent’s licence. About a person: nothing, to a third party.
Members, directors and beneficial owners — held by the registered agent, not the authority.
Certificate of incumbency dated within 90 days, plus an agent letter naming the beneficial owner.
Existence and good standing, for a fee.
Members, and the BOSS beneficial-ownership filings — held for the authorities.
Certificate of good standing, plus an agent confirmation of members and beneficial owners.
Licence status, trade name and activity.
Shareholders and UBO declarations.
Licence extract, plus an attested share register.
Directors, shareholders and annual filings.
Beneficial owners, since public access was suspended.
A certified UBO extract obtained by the company.
Six steps, run on the demonstration case C-DEMO-SC-ORION. A person appears exactly once, at the end.
one field, any number of files, in any language.
ownership to the ultimate owner, breaks drawn as breaks.
registers, sanctions and PEP lists, and the issuer itself where the issuer will confirm. Every answer stored whole, with its date.
against your requirement set, jurisdiction pack and risk matrix. Each versioned. Each stamped on the result.
with its reason and with the substitute the jurisdiction accepts in its place.
recording a decision, and countersigning it, are human acts.
Every platform publishes met, not met and in progress. Evix adds a fourth: the requirement was checked and cannot be established — recorded with the source that was asked, why that source cannot answer, the substitute the jurisdiction accepts, and the date.
Seychelles keeps beneficial ownership with the registered agent. No third party can lawfully query it. A blank field says you didn't look. A documented outcome says you did.
Beneficial ownership is held by the registered agent. A third party has no lawful route to query it.
Substitute accepted by the jurisdiction: registered agent certificate of incumbency, dated within 90 days. Asked 03.09. Answer stored whole.
The audit log is append-only and hash-chained. On signature, the root hash is signed with your instance key, so a supervisor can confirm the file is the one signed that day without contacting us. The day’s root is signed with our own key and published: keep a copy of one day, and every day after it can be checked against what you kept. Only the hash is published. The facts never leave your tenant. In this demonstration deployment no signing key is configured: the file ships as an unsealed draft, and the chain below is verified by recomputation alone.
Over MCP, two counterparties can establish that each meets a shared requirement set without either seeing the other's case file. The tools that return findings and assessments are not filtered out of the counterparty's surface; they are absent from it. The boundary is the tool set, not a prompt asking nicely.
the record you will be asked for, written while the decision is made rather than reconstructed afterwards.
the cases that have been open for eight days, closed with a reason either way.
roles enforced in the database, a documented API, and a tool surface that cannot leak what it does not expose.
Evix has run live cases with pilot clients, against their policies and their stalled queues. The first published metric will be a pilot's own figure — measured on their queue, named, dated and signed off by them. The slot for it is drawn and waiting.
the rule that keeps an invented fact out of a decision file keeps an invented figure off this page.
Pick the pack your team keeps reopening. We will run it live against your policy, show every source, and show you exactly what can be established and what cannot. You keep the file either way.