AI Scenario Migration RFC
A template for moving a scenario from MaaS to self-hosted or hybrid execution.
Purpose
Use this RFC before buying GPUs or moving traffic. The goal is to prove that the scenario keeps quality, SLO and economics in the new boundary.
Fields
scenario
scenario_id
What is moving and which user outcome must hold.
owner
Product owner
Who accepts scenario quality and product risk.
current
Current route
Baseline model/provider, cost, latency and quality.
candidate
Candidate model
How the candidate was found: MaaS, OpenRouter, benchmark or internal eval.
draft
self-hosted draft status
Whether a rough local version is up and the scenario reproduces.
evals
quality baseline and eval dataset
What is compared and which errors block rollout.
slo
Latency SLO
TTFT, TPOT, total latency, p95/p99 and latency class.
cost
Cost baseline
Current cost, non-production capacity, reserve and expected utilization.
route
Route policy
route_lane, fallback route, canary plan and stop criteria.
incident
Owner of incident
Who decides rollback and owns the review.
Readiness Criteria
- ✓Current quality and cost baseline is known.
- ✓A rough self-hosted candidate reproduces the scenario.
- ✓Eval dataset and stop criteria exist.
- ✓Fallback route and canary plan exist.
- ✓Non-production capacity is included in economics.