Production AI Platform Map
The twelve-responsibility map from use cases to ownership.
From API key to platform.
Production AI is not a model. It is a platform. This is a practical map for teams building LLM, STT, embeddings and agent systems in production: inference, routing, cache, evals, guardrails, observability, cost and ownership.
14
chapters and maps
12
platform layers
5
content formats
3
tools
4
role tracks
Product use cases
AI Gateway
Provider strategy
Execution-path routing
Inference runtime
Caching
Do not read it linearly. Start from the platform problem in front of you.
Open the platform map and locate the missing responsibility.
Use the maturity model and MaaS vs self-hosted strategy chapter.
Start with inference economics and prefix cache.
Use AI Quality Gate, observability and ownership chapters.
Pick the path closest to your current responsibility, then use the catalog below to filter materials.
Ownership, platform map, quality and economics.
Strategy, maturity and operating model.
Gateway, observability, tools and production contracts.
Serving, STT, embeddings, cache and capacity.
Handbook navigator
Progress
0/22
read
0
bookmarked
Local progress only. No account, tracking or backend.
Search
Formats
Role tracks
The twelve-responsibility map from use cases to ownership.
Seven levels from one API key to AI-native operations.
Choose the first chapter by the platform problem in front of you.
Why production AI should be treated as a platform, not a model choice.
A strategy decision, not a religious argument.
The control point for access, quotas, routing, policy and cost.
Route execution path, not only model names: direct, RAG, agentic or human review.
Serving decisions around LLM, STT, embeddings and rerankers.
Treat speech-to-text as a first-class production workload.
Embeddings and rerankers as a quality, latency and lifecycle layer.
Cost per accepted outcome, not raw token math.
How prompt shape, tool schemas and routing decide cache behavior.
A rollout loop that prevents silent quality degradation.
Minimum telemetry for model, prompt, cost, latency and outcome.
Policies, telemetry, fallback and ownership, not one magic library.
Who owns quality, cost, incidents and platform contracts.
Client-side diagnostic for unstable prefixes and schema drift.
Estimate effective cost with cached input tokens.
Local readiness review before rollout.
A template for moving a scenario from MaaS to self-hosted or hybrid.
Release notes, quality gate, fallback and cost profile for model changes.
Dataset, error taxonomy, regression deltas and rollout recommendation.
Production, stage, debug, canary, reserve and cost per accepted outcome.
A reusable matrix for MaaS, de-identified MaaS, self-hosted, batch and hybrid.
A postmortem template for prompt, model, tool, cost and safety incidents.
The map has twelve responsibilities. If one is missing, a product team will implement it locally.
L01
Scenario intake, user value, risk profile, acceptance criteria.
L02
Unified API layer for auth, quotas, routing, policy, cost attribution.
L03
MaaS, OpenRouter-style research loops, self-hosted and hybrid decisions.
L04
Choosing the lane: small model, large model, RAG, agent, human review or policy denial.
L05
LLM, STT, embeddings and reranker serving with latency and throughput budgets.
L06
Prompt cache, prefix cache, KV-cache and stable request shape.
L07
From research to shadow, canary, production, rollback and retire.
L08
Datasets, eval suites, regression checks, canary rollout and feedback loops.
L09
Traces, tokens, TTFT, TPOT, fallback events, safety events and feedback.
L10
Scenario cost, cached tokens, retries, GPU utilization and cost per accepted outcome.
L11
Policies, PII, prompt injection, tool risks and audit trail.
L12
Ownership, SLOs, incidents, capacity planning, runbooks and platform DevEx.
Foundational chapters for the first public version.
The responsibility-first map: from use cases to gateway, inference, evals and ownership.
A leadership framework from one API key to AI-native operating model.
A strategy chapter for choosing managed, self-hosted or hybrid serving.
How to choose direct, RAG, agentic or human-review execution.
The handbook is meant to become maps, checklists, templates and small diagnostic tools.