FrameworkCross-Border AI Architecture PatternsSheet 59

A residency rule is not a blocker. It is a determinant.

Four deployment architectures for multi-jurisdiction AI.

← Defensible AI

§ 01Status

What this is.

REG-09 · Cross-Border AI Architecture Patterns™

Position in the architecture · data residency

Specification · No standalone specification is deposited for this framework. Its authoritative treatment is Chapter 9 of the Enterprise Playbook, ISBN 978-1-0678960-1-0. This page and registry entry REG-09 are the most complete normative statement available in citable form.

The boundary, optimizer and evidence model Three stacked blocks. At the top a governed boundary states what may not happen and moves only by governance, never by optimization. Beneath it the optimization space, where cost, latency, quality, throughput and autonomy are free to move but cannot exit the boundary. At the base, evidence records what happened and why, proving the boundary held. An arrow on the left shows that widening autonomy widens the optimization space rather than relaxing the boundary. An arrow on the right shows evidence returning to governance as the only route by which a boundary may move. The boundary, optimizer and evidence model Nabeel Khan 2026 https://doi.org/10.5281/zenodo.22109864 https://doi.org/10.5281/zenodo.22109864 Copyright 2026 Nabeel A. Khan. Licensed CC BY 4.0. Nabeel Khan https://nabeelkhan.com/frameworks/pattern-language A BOUNDARY IS A CLAUSE THE OPTIMIZER MAY NOT CROSS Governed Boundary what may not happen moves only by governance, never by optimization constrains Optimization Space cost · latency · quality · throughput · autonomy free to move within the boundary, and unable to exit it produces Evidence what happened, and why proves the boundary held autonomy is raised by widening this space, never by relaxing the boundary above evidence is the only route by which a boundary moves Every pattern in Section 4 is an instance of this figure, declaring its boundary, its optimizer and its evidence in that order. A Pattern Language for Production LLM Platforms v1.1 · Nabeel Khan · nabeelkhan.com/frameworks/pattern-language · CC BY 4.0 · DOI 10.5281/zenodo.22109864
Figure 1. The Boundary Invariant. This framework is its worked instance, which is why it sits under an engineering law rather than under a governance altitude.
§ 02Boundary and optimization

Boundary and optimization.

Residency is the boundary. The topology is the optimization. The four patterns are four optimizations under one uncrossable clause, which is why this framework sits under the Boundary Invariant rather than under a MESA altitude, and it is the only one of the nine that does.

§ 03Four patterns

Four patterns.

Sovereign Silo keeps everything within one jurisdiction. Federated keeps data in place and moves computation. Regional Hub consolidates within a permitted region. Hybrid mixes them per workload. Selection runs by enumerating the boundary set per jurisdiction and classifying each workload against it, and the BOE Declaration at the fourth step is what makes routing evidence usable during a reconstruction rather than merely available.

§ 04Honest limits

What this does not claim.

Asserted, and time-sensitive. Jurisdiction-specific transfer rules age. Every regulatory assertion must be re-verified against primary sources at the time of use, and a boundary set carried forward from a prior deployment without re-verification is not a boundary set. This page names no jurisdiction-specific rule, deliberately.

Asserted. The worked cases in the source treatment are disclosed as composites. They illustrate the selection method and are not evidence that any named institution operates any of the four patterns.

Missing. No decision instrument exists, so the method cannot be applied consistently by two architects working independently.

§ 05Cite

Citation.

Cite this framework. No standalone specification is deposited. Its authoritative treatment is Chapter 9 of the Enterprise Playbook, ISBN 978-1-0678960-1-0, and its normative statement in citable form is registry entry REG-09 in 10.5281/zenodo.22170112.

§ 06Where this sits

In the practice.

§ 10Ask an assistantLive, no key

Ask your AI assistant instead.

This page is a snapshot, accurate at the release it cites. The same corpus is callable, publicly and without a key, so an assistant can query it live and return an answer carrying the source it came from. For this page that is explain_this_setup and search_knowledge, which do what this page describes rather than describe it again: the first returns how this site's machine layer is actually built, component by component, and the second queries the corpus behind this page and returns matches with the URL each came from. The page states the practice; the tools are the practice.

01 · Connect
claude mcp add --transport http concylium https://mcp.nabeelkhan.com/api/mcp

Claude Desktop, ChatGPT, Cursor, VS Code and Gemini CLI take the endpoint on its own: https://mcp.nabeelkhan.com/api/mcp. No key, no account, nothing to sign. Setup for every client.

02 · Ask

“Using Concylium, call explain_this_setup and tell me whether this site actually implements what its machine-accessible-ai-expertise page claims.”

A category page that survives being audited by the reader's own assistant is doing something a brochure cannot.

Fin · Machine-Accessible Expertise
Point your assistant at the endpoint →