MODEL ROUTING + PROVIDER PORTABILITY
Agents bind to logical model aliases while the Model Gateway resolves qualified providers, model capabilities, deployment profile, policy, context window, tokenizer, availability and cost constraints. Provider-specific details stay outside the core product contract.
Logical model aliases and the Model Gateway are accepted architecture decisions; concrete provider choices remain lifecycle-qualified adapters.
LOGICAL MODEL ALIASES
Agent and team definitions reference logical aliases and declared model capabilities. Provider names, endpoints and credentials stay in deployment-specific routing configuration instead of leaking into reusable product contracts.
QUALIFIED ROUTING
A route is eligible only when the provider and model are qualified for the deployment profile, data class, region, required feature set and current runtime policy. Unsupported paths return explicit incompatibility instead of hidden substitution.
CONTEXT COMPATIBILITY
Context window, tokenizer, structured-output and serialization compatibility are part of the routing decision. Mandatory context that cannot fit produces an explicit context-budget error rather than a silent move to a larger or external model.
LIFECYCLE + EXIT
Technology fitness, cost, latency, policy and health signals can trigger review. Migration uses compatibility tests, shadow or canary evidence, rollback and exit criteria while stable Projera contracts protect the product layer from vendor-specific rewrites.
