Capstone — Operations Runbook (Component 17)

The ops runbook for the platform. Based on the incident runbook template and Phase 7.10. Fill <...> for your deployment.

System map

  • Components: gateway, product app, RAG, agent, vLLM/local, vector DB, cache, Postgres, providers.
  • Dashboards: <links: p95/p99 latency, cost per request/tenant, error/fallback rate, GPU util, cache hit>.
  • Correlation ID: propagated request→retrieval→model→tools (reconstruct any request).
  • Status page: <link>.

Alerts → first response

AlertLikely causeFirst action
p95 latency ↑provider slow / KV pressure / batchfail over provider; scale serving; reduce batch/context
Error/fallback rate ↑provider outage / rate limit / bad deployconfirm fallback firing; rollback; check limits
Spend spikeagent loops / power user / routing changeattribute by tenant/feature; cap; fix driver
Safety violationguardrail gap / jailbreaktighten guardrail (fail closed); red-team; patch
Cross-tenant leakisolation filter gapdisable path; fix filter; audit blast radius; notify
Eval regression (CI)prompt/model changeblock deploy; roll back to last-good

Incident loop

  1. Detect (alert/report) → declare severity.
  2. Investigate → reconstruct via correlation ID; dashboards + audit logs.
  3. Contain → fail over / disable feature / revoke key / rate-limit.
  4. Remediate → fix root cause; verify with eval + red-team.
  5. Communicate → status page; customers; (data incident) regulators within deadlines.
  6. Postmortem → blameless; add a regression test / eval case.

Routine ops

  • Deploys: canary a fraction → watch p95/error/eval → promote or rollback. Models/prompts are versioned.
  • Model bake-offs: scheduled re-eval vs new models on the golden set (12.08).
  • Cost review: weekly cost-per-resolved-task + margin; tune routing/caching.
  • Key rotation: scheduled + on suspicion; config change, no redeploy.
  • Index freshness: RAG re-index job; monitor staleness.

Quick levers

fail over provider · toggle caching · adjust rate limits/quotas · scale app/serving pods · tighten guardrails (fail closed) · revoke a key · roll back model/prompt version.

SLOs (set yours)

SLOTarget
p95 latency<ms>
Availability<99.9%>
Error rate<%>
Eval score (golden set)<≥ X, gate>

Escalation

SeverityWhoWhen
SEV1 (down / data leak)<lead + on-call>immediately
SEV2 (degraded)<on-call>within <X>