# SLO policies

SLO policies are immutable revisions. Changing objective, threshold, window, population minimum,
severity or environment deactivates the prior revision and creates a new fingerprinted revision.
Historic evaluations keep the exact prior policy ID.

## Initial active policies

| Key | Environment | Objective/threshold | Window | Minimum | Rationale |
| --- | --- | --- | ---: | ---: | --- |
| `platform.api.production` | PRODUCTION | 99% | 24h | 20 | local control-plane availability |
| `gateway.production` | PRODUCTION | 99% | 24h | 20 | valid capability routing |
| `rag.embedding.production.success` | PRODUCTION | 99% | 24h | 20 | established stable capability |
| `rag.embedding.production.latency` | PRODUCTION | p95 ≤ 1000 ms | 24h | 20 | measured warm/shared-GPU envelope, not a quality gate |
| `gpu_node.production.freshness` | PRODUCTION | 99%, max age 90 s | 1h | 1 | existing 30/90 receive-time contract |
| `scheduler.production.correctness` | PRODUCTION | 99.5% | 24h | 20 | typed refusal is valid; internal failure is not |
| `migration.production.reliability` | PRODUCTION | 99% | 7d | 1 | failure/manual intervention consumes budget |
| `vision.embedding.lab` | LAB | 95% | 24h | 5 | operational LAB signal only |
| `speech.transcription.lab` | LAB | 95% | 24h | 5 | operational LAB signal only |

Thresholds use the established node liveness contract and M5–M13 measured behavior. They are not
selected after a failure merely to make the platform green. LAB policy evaluation conveys operating
evidence without production readiness or an availability budget. `BACKGROUND` is supported by the
contract for migration/benchmark work but has no initial production objective.