# Model routing policy ops kit

Use this kit to operate model routing as policy rather than ad hoc provider choice. It connects workflow needs, data classes, quality gates, latency budgets, fallback behavior, cost ceilings, and owner approvals.

## What it includes

- A route table for workflow, data class, provider, model, fallback, quality gate, latency budget, and cost ceiling.
- An exception log for routing overrides and degraded providers.
- A schema for model choice, constraints, release evidence, and owner approval.
- A review brief for provider changes and routing decisions.
- A signal map for quality, latency, cost, fallback, incidents, and data-boundary events.

## How to use it

Define the route table before production traffic. Review route changes like releases: require evaluation evidence, rollback plan, and owner approval. Monitor routing exceptions for cost, quality, and data-boundary drift.