Model routing.
Task-appropriate model selection across the major foundation-model APIs — Anthropic, OpenAI, and models on AWS Bedrock — under your cloud account.
Layer 02 — The ArchitectureQ3 2026
Orchestration.
Routing, model selection, and prompt management — the right model and the right context for the right query.
Orchestration is Layer 2 of the ism3 stack. Routing, model selection, prompt management. Coordinates the right model and the right context for the right query.
Between your applications and the model APIs sits a set of decisions most deployments make implicitly: which model handles which task, what context travels with the query, which prompt version is live, and what happens when a provider degrades. Layer 2 makes those decisions explicit, versioned, and operable.
Orchestration is also where cost and quality get governed. Routing high-stakes queries to stronger models and bounded work to faster ones is an architectural choice — one that should be reviewable, not buried in application code.
Inside Layer 2.
Prompt management.
Prompts are versioned, reviewed artifacts with a deployment history — not strings scattered through application code.
Context assembly.
What the model sees per query is composed deliberately from Layer 3 retrieval, carrying the access controls that came with it.
Operational controls.
Timeouts, retries, fallbacks, and degradation behavior — defined and observable, so a provider incident is a slow answer instead of an outage.
Reference architecture
Whitepaper — Q3 2026.
The Layer 2 whitepaper will document the routing architecture, prompt lifecycle management, and the operational controls that sit between enterprise applications and foundation-model APIs.
FAQ
Layer 2, answered.
Major foundation-model APIs — Anthropic, OpenAI, and models on AWS Bedrock — under your account. We do not train, fine-tune, or host models, and your data never leaves your tenancy for any purpose.
Because prompts change model behavior the way code changes application behavior. In regulated workflows that means versioning, review, and rollback — the same discipline as any other deployment artifact.
Degradation behavior is defined at Layer 2 — routing, fallback, and failure modes are part of the design rather than an incident-day improvisation.