---
name: undominated-slo-error-budget-depletion-audit
description: "Audits 30-day Service Level Objective (SLO) error budget burn rates to trigger automated traffic shedding. Recomputed fields must match the other inputs. A pass is not a compliance, safety, or price verdict."
license: MIT
metadata:
  author: Undominated.ai
  version: "1.1.0"
---

# SLO error budget depletion audit

## Description
Audits 30-day Service Level Objective (SLO) error budget burn rates to trigger automated traffic shedding.

## Category
`serving`

## Tags
`serving`, `slo`, `error-budget`, `burn-rate`, `sre`

## When to Use
Audit SRE monitoring systems to ensure error rate spikes trigger alerts before exhausting monthly budgets.

## Operational Limitations
Calculates multi-window burn rates from telemetry inputs; does not configure Prometheus alert rules.

## Verification Script
Run the deterministic verification checker:
```bash
python3 scripts/check.py examples/synthetic.json
```
Exit codes:
- `0`: Check passed and thresholds satisfied.
- `1`: Threshold breach or operational violation detected.
- `2`: Schema error or invalid usage.

## What the checker recomputes

These declared fields must match the other inputs. The tolerance is 0.02, or 0.1% of the recomputed value when that is larger.

- `burn_rate` = div(measured_error_rate_1h, error_budget_total)

The original threshold checks still apply:

- `burn_rate` must not be > `max_allowed_burn_rate`.

Every other declared field is type-checked. A negative value is rejected except for deltas, drifts, and gains. A type check does not, by itself, prove the measurement.

`population` and `observedAt` are required. The bundled examples are synthetic fixtures, not market measurements.

```bash
python3 scripts/check.py examples/synthetic.json
python3 scripts/check.py examples/contradiction.json
python3 scripts/check.py examples/broken.json
```

Exit 0 is a pass, exit 1 is a review, and exit 2 is invalid input. A pass does not certify a provider, a regulation, a release, or a price.
