Models, Providers & Routing
Choose execution strategies and providers without making the provider the architecture.
Primitive has a Model Gateway provider registry, truthful integrated/unavailable state, deterministic execution strategies and Role Router planning.
Primitive can choose different engines for different jobs, but the rest of the car should not have to be rebuilt whenever you swap the engine.
Provider choice is treated as a routing/execution concern below the stable Primitive contracts. This allows cost, quality, latency and assurance strategies to change independently from work objects, permissions and causal records.
Model Gateway
The provider registry records which integrations are actually available. Planned adapters such as additional local or external providers are not represented as integrated until they use the governed path.
Execution strategies
Efficiency, Performance, High Assurance and Experimental strategies provide deterministic policy choices around execution without binding the product model to a vendor.
Role routing
Role Router and deterministic route planning are part of the canonical Workspace release. Expert-routing research builds above this foundation.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.