The previous post in this series argued that each jurisdiction has to be built native, never translated. That raises an obvious engineering question: if every market is its own build, are you maintaining a separate product per country?

No. There is one engine. What differs per market is walled off inside it. This post is about how those two facts live together.

Shared where it should be shared

Some things do not vary by jurisdiction. How matter data is stored in the browser. How the privilege gate sits in front of every outbound AI call. How the interface is laid out, how documents are assembled, how a matter moves through its stages. That machinery is one codebase, shared, because rebuilding it per country would mean a fresh chance to get the security model subtly different in each — and the security model is the one thing that must be identical everywhere.

So the core engine is common. A fix to how matter data is protected protects every market at once. That is the point of sharing: the safety-critical parts are written once and hold everywhere.

Walled where it must be walled

The legal content is the opposite. UK statutes, UK regulator language, and UK templates live on the UK side. Each other market's statutes, its own professional voice, and its own confidentiality duty live on that market's side. These do not cross-reference. UK code never reaches into another market's legal content, and that market's code never reaches into UK content — not as a convention someone might forget, but as a boundary the build enforces.

Because the risk here is specific and nasty: bleed. UK content quietly citing another market's statute. Another market's content naming a UK regulator. A phrase that is a translation calque rather than native drafting. Each of those is a small error that reads fine and is wrong, and each would undermine exactly the trust the product exists to earn.

So we scan for it. A detector walks landed code for cross-jurisdiction string-bleed and fails the change if it finds any — one market's content referencing another's statutes verbatim, one market's content naming another's regulators, translation calques. The privilege gate is checked the same way: every outbound-call site is classified against its market's rule — legal professional privilege as a soft warning where the law allows judgement, an absolute-confidentiality duty as a hard block where a market's law makes it absolute. A bypass fails the build. The wall is not a promise in a document; it is a gate in the pipeline.

How new markets open on the same core

This is what lets a new market open without a new product. The shared engine is already built and already safe. Opening a market means authoring its native legal content — its statutes, its voice, its compliance pack, its templates — behind the same wall the existing markets sit behind, and letting the same detectors confirm nothing bled across.

The UK is native and live on this architecture today; further markets are being prepared the same way — native content, walled, on the shared core. The engine does not get rewritten for each. The wall does not get relaxed for any.

Why it is built this way

The lazy version of "multi-market" is one legal brain translated outward — cheap to claim, wrong in the places that matter. The honest version is one engine, many native legal builds, hard walls between them, and automated checks that the walls held.

It is the through-line again: built by solicitors, for solicitors, not a generic tool with a legal skin. The skin would translate. The engine walls the jurisdictions apart on purpose, and proves it did.

← All posts