Compute Locality

Locality determines jurisdiction, latency and cost simultaneously, and organizations usually consider only the last. A request processed in another jurisdiction may be lawful, unlawful or lawful-with-conditions depending on the content, which makes locality a classification-dependent decision rather than a single architectural choice. Systems that treat it as a global setting cannot express the policy most regulated organizations actually have: some content anywhere, some content here only.

Because model selection in Centralpoint happens per request and embedded local models are available alongside cloud providers, locality can follow classification — sensitive categories routed to local inference while general work uses whichever provider is most economical.