Who is really behind Aurelia — and why a case that was cleared on its merits still becomes an incident.
A corporate client the relationship manager needs onboarded by tomorrow. Nothing about it is what it seems.
Customers change overnight — a sanctions match, adverse media, a move to a high-risk country — and the graph notices first.
The work that buries a unit — onboarding, 412 alerts a night, 2,412 remediation files — done by agencies, decided by people.
Every scene carries its story's colour. The map at the top of each slide shows where we are in the day.
Two of them — Caspian and Helios — have never been in the same case. Watch what happens at 09:16.
and shows its working — every step, every source.
something nobody asked for — before anyone opens the case.
see it — a link no single system or case contains.
At five o'clock we will check: there were six moments only a graph could produce. How many will you spot?
What changed overnight — and what actually matters?
A new retail customer — or someone the bank has already met?
Who is really behind Aurelia?
Found by the Corporate Structure agency walking the chain, and by the Fabric linking two cases. The customer supplied the share register at 10:05.
Can the relationship manager get a shortcut to meet her deadline?
One graph, two meanings. Nothing hidden from Sophie, nothing added for Tomasz.
Cleared at 10:48 — owned by a PEP's spouse, linked to a sanctioned network, a shortcut refused at 10:30.
Nordvik, Baltic and Helios were pushed at 08:30. Next: what they mean.
Ade onboarded in three minutes. Next: 412 alerts, then 2,412 remediation files.
Questions so far?
How many of last night's alerts actually need a person?
Baltic moved to a high-risk country. Is that the whole story?
How much of a remediation can close without calling a single customer?
A transaction against a case state is an incident — whatever the case later decides. Cleared on its merits does not clear 10:31. It goes to the second line, and stays open.
Every one of you has had this. Most of you found it at audit.
Who checks the agencies?
Each circle is a case as it evolved today. Each chord is an inference between cases — one was re-determined without anyone opening it.
Marcus sees the whole book. Tomasz sees Helios without the sanctioned parent. Sophie sees Aurelia alone — what a person may not see is absent, not dimmed.
None of it was drawn by hand. Every link carries its evidence — and tomorrow starts from here.
Each system sees its own record. The graph sees the customer, the network, and the links between cases.
| Before | With DataFab | |
|---|---|---|
| Retail onboarding · analyst time | 40–60 min | 3 min |
| Corporate onboarding · elapsed | 3–5 days | 93 min |
| Alerts needing a person | 412 | 71 |
| Periodic reviews re-performed | 214 | 66 |
| Remediation files touched by an analyst | 2,412 | 19 |
| Quality-control coverage | 5% · 2 weeks late | 100% · same day |
Illustrative operating baseline · in deployment, these become your own volumes and times.
A migration programme: copy the estate, map it to a vendor model, build pipelines — quarters before the first governed decision.
Read in place inside your boundary; ontology derived from your data. Weeks, not quarters, to a working Monday.
Vendor engineers on site to build the work and extract the data — and back again every time the policy changes.
Your people and your partner compose the agencies in the Knowledge & Agentic Studio. No vendor team on site.
A copy to run, reconcile and license by volume, on top of the systems you already pay for.
Depending on volume — agencies carry the work, people take the decisions that need a person.
Unwind the copy, rebuild resolution and logic elsewhere, re-integrate — a programme of its own.
Systems of record never touched. Export the identity layer, rules, decisions and audit trail — in days.
Against market-standard costs at each stage · illustrative · run reduction varies with volume · validated against your own estate and volumes in the proof of value.
Ask to see any part of the day again — including 10:31.
Each phase has an owner and an exit gate. Gates that cannot be waived: raw data leaving the boundary 0 B · every source manifest complete · no merge on a name alone · every refusal produces a record · the customer approves every release.