ROUTE SHEETS · CATALOG VERSION PLANNING-2026.08Know what is fixed.
Know what is pending.
Each route class is a planning boundary, not a connected supplier. A production route exists only after the model, provider, region, data terms, capacity and failover behavior are named in writing.
GLOBAL VALUEPLANNING · SUPPLIER PENDING
Approved non-sensitive batch and asynchronous work
- Model boundary
- Open-weight and commercial model families; exact version must be named in a quote
- Processing region
- Global candidate set; countries and subprocessors not yet approved
- Data eligibility
- Public, synthetic or minimized non-sensitive business data only
- Retention / training
- No public commitment; supplier evidence and written terms required
- Failover
- Not configured
Scope this route →GLOBAL BALANCEDPLANNING · SUPPLIER PENDING
Recurring interactive support, search, RAG and agent workloads
- Model boundary
- Commercial or open-weight model class; alias and version bounds require approval
- Processing region
- Multi-region planning concept; actual processing locations must be disclosed
- Data eligibility
- Qualified business data after workload review; no regulated data by default
- Retention / training
- No-training and retention terms are route-specific and unconfirmed
- Failover
- Candidate design only; not promised
Scope this route →U.S. PROTECTEDPLANNING · SUPPLIER PENDING
Workloads requiring a declared U.S. processing boundary
- Model boundary
- Allowlisted family and version bounds in the final route schedule
- Processing region
- Requested U.S. processing; provider, support and telemetry locations must be verified
- Data eligibility
- Controlled business data only after security and legal review
- Retention / training
- Written retention, logging and training restrictions required before traffic
- Failover
- U.S.-only failover must be separately designed and tested
Scope this route →