The boundary with exactly one gate

A customer's security team sends over a questionnaire before they will sign. Buried in it: list every system that touches this data, and name who can see it at each step. Someone in IT pulls an answer together from memory and old vendor contracts, because nobody drew this down when the project started.

The diagram that finally goes back has a box labelled "the cloud" with an arrow pointing at it, and nobody on the call can say with confidence who sits on the other side of that arrow, or whether that vendor can change the deal next year. The meeting ends without a signature. Not because the AI did anything wrong. Because nobody could show where it lives.

Why we build it this way

"Sovereign" gets used as an adjective, attached to any product with an on-premise option. We think it should be a drawing, not a word. Not a general assurance that the AI is secure, or that a vendor does not train on your data. A literal diagram: every boundary your data crosses, and who controls the far side of each one.

The obvious answer is to trust a vendor's word, sign the agreement, and move on. That hands control to whoever administers the far side of a boundary you never drew yourself. Once you cannot draw it, you cannot audit it, you cannot switch it off, and you cannot honestly answer the question customers are starting to ask before they sign anything: where does our data actually go?

So we draw the boundary first, before choosing a tool or a vendor. What sits inside it, and the single point where anything is allowed to cross. Everything else gets built to fit inside that drawing, not the other way round.

How it works, roughly

Inside the boundary sit the runtime that answers questions, the agents that act on what it finds, and an unbroken record of everything either one has touched. Nothing about this is a metaphor added after the fact — it is the actual deployment, and it becomes a document you can hand to an auditor or a customer's security team as it stands. That document names:

• Every boundary the data crosses, and who controls the far side of it
• The one gate anything is allowed to pass through, and who approved that crossing
• The record of what has crossed, kept inside the boundary, not in a vendor's logs you cannot read

When someone wants an exception — a new integration, a vendor who needs a feed — that becomes a new line on the drawing, decided and signed off, rather than a workaround nobody wrote down. Disagreement does not get resolved by finding a way around the boundary. It gets resolved by redrawing it, and having a person sign the new version.

A year of this is a document you already have when a customer or a regulator finally asks the question, instead of a meeting that ends without a signature. What crosses the boundary is still a person's decision, and the record of it stays inside walls the customer already owns.

AI Transformation · drag to turn