FrameworkCross-Border AI Architecture PatternsSheet 59

Cross-Border AI Architecture Patterns.

A residency rule is not a blocker. It is a determinant. Four deployment architectures for multi-jurisdiction AI.

← Defensible AI · How the nine relate

§ 01Status

What this is.

REG-09 · Cross-Border AI Architecture Patterns™

Position in the architecture · data residency

Specification · Deposited. 10.5281/zenodo.22285049, CC BY 4.0.

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.

§ 04Where it applies

Which institutions, and on whose authority.

Scoped to this sector by the specification

Cross-Border applies wherever a residency constraint exists, which makes its boundary a deployment shape rather than an industry. It is the only framework in the family that sits under the Boundary Invariant rather than under a MESA altitude, and that is why: the constraint is architectural, not institutional.

Where it bites · Any multi-jurisdiction deployment

§ 05How it has changed

The record of its own revisions.

A framework that cannot say how it changed reads as though it never has. This is drawn from the registry entry, which versions itself independently of the specification it points at.

Change history

  • 2026-08-30 · entry v1.0 — First registry entry
  • 2026-08-30 · entry v1.0 — Records the repositioning from peer framework to worked instance of the Boundary Invariant
  • 2026-09-15 · entry v2.0 — Specification status moves from `source-treatment` to `deposited` on the deposit of the Cross-Border AI Architecture Patterns specification, whose concept DOI the entry now carries
  • 2026-09-15 · entry v2.0 — Scope phrase and definition reconciled with that specification, which governs the count under 11.3: three patterns are selectable at the level of a workload class and Hybrid is the composition of an estate, not a fourth pattern
  • 2026-09-15 · entry v2.0 — The `missing` limitation recording no decision instrument is closed by Section 4 of that specification
  • 2026-09-15 · entry v2.0 — Receives an authority grant from REG-07, closing the gap that specification records at 8.2 rather than working around

Limitations recorded in the registry

  • Jurisdiction-specific transfer rules cited in the source treatment age. Every regulatory assertion MUST be re-verified against primary sources at the time of use.
  • 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.
  • Governs where inference and data may sit. Does not specify infrastructure, network architecture or the contractual arrangements by which a topology is procured.

What would show this to be wrong. The Cross-Border Patterns are falsified if a real boundary set requires a per-workload assignment in which some workload class can be served by none of Sovereign Silo, Federated or Regional Hub. Hybrid is not a fourth alternative for this purpose. It is defined at 4.9.5 as a composition of the other three, taken per workload class, and it therefore inherits their coverage rather than extending it. The claim under test is that the first three exhaust the topologies available under a residency constraint at the level of a single workload class, and a workload class none of them can serve would refute the enumeration directly. Stating the condition against Hybrid's composition rather than against the four as a set is deliberate, because a catch-all cannot be falsified.

§ 06Honest 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.

§ 07Cite

Citation.

Cite this work. Cross-Border AI Architecture Patterns, version 1.0. 10.5281/zenodo.22285049. This is the concept DOI and it always resolves to the latest version. CC BY 4.0.

§ 08Where 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 →