Private and sovereign execution

Overview

Privacy objectives and hard region/provider constraints determine eligibility before route ranking. Sovereign is a routing boundary, not a marketing synonym for security.

• Classify data before it enters a prompt.
• Restrict allowed regions and providers explicitly.
• Use private or local-only objectives only with configured eligible capacity.
• Verify logs, storage, support access, and provider contracts end to end.

Production checklist

• Keep credentials in a server-side secret store.
• Set explicit cost, latency, privacy, provider, and regional constraints.
• Capture route and evaluation evidence for incident review.
• Test timeouts, cancellation, fallback, and denied-policy paths before rollout.