Request jurisdiction and provider selection
The decision record identifies the serving provider, country and policy permitting that location.
Seven notes answering buyer and reviewer questions. The notes can be checked against the catalogue.
The decision record identifies the serving provider, country and policy permitting that location.
All notes
The obligation is contractual rather than approval-based, and a signed clause does not guarantee residency.
Chinese models served from American data centres address a different processing-location requirement from East Asian in-region workloads.
Fail-closed routing refuses requests when no provider is eligible in the required jurisdiction.
DeepSeek on AWS and DeepSeek on Alibaba Cloud use the same weights but carry different legal positions. Combining them in one catalogue entry defeats the purpose.
The inference call is usually compliant. The boundary often breaks in web search, code execution, or a retrieval hop.
Prefix reuse is the largest single cost lever in inference. It also moves data, so it belongs on the same side of the boundary as the rest of the request.
Routing
How the decision is made, and why the order matters more than the model choice.
Compliance
What the law requires before a prompt crosses a border, including transfer mechanisms.
Architecture
Where residency leaks in real pipelines: tools, caches and media stages.
Start