<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 29_CONFIGURATION_OMNIROUTE.md -->

Configuration & OmniRoute

Configuration principle

Use one canonical compiled configuration contract.

Do not maintain independent application-specific provider configuration when the platform already owns it.

Flow

Environment
→ Organization Configuration
→ Tenant Configuration
→ Compiled Configuration
→ Stable Platform Contract
→ OmniRoute
→ Runtime

OmniRoute

OmniRoute resolves:

• service;
• capability;
• provider;
• model;
• execution binding;
• fallback.

Applications should not hardcode provider routing.

Configuration areas

Identity
Connectivity
AI
Execution
Governance
Storage
Observability
Billing / Metering
Feature Flags

Principle

Provider choices remain implementation details behind stable platform contracts.