The framing debate is stale. AI safety is not a philosophical question awaiting an answer — it is an engineering discipline, and one with decades of safety-critical precedent. Aviation, nuclear power, and distributed systems all build safety under uncertainty. None of them solved it; all of them manage it, continuously, through failure modes, margins, and monitoring. That is the frame worth working in.
Safety is not a property of the model alone, settled after training. It is a property of the system the model runs inside. Some controls are settled engineering — rate limits, human-in-the-loop approval gates, blast-radius containment, least privilege: reliability controls distributed systems has shipped for decades, and they work. Others are genuinely new: output classifiers and prompt-injection defenses exist only because this component exists. They are young, and adversarial pressure makes them an active arms race. Treating the second class as though it were the first is the present failure mode.
Control failures come from two directions. One is old: known controls get skipped when teams ship fast — write access without blast-radius thinking, irreversible operations without dry-runs. Circumspection remains the binding constraint, as it always has been. The other is new: the component is probabilistic and adversarially pressured, so semantic controls could not simply be borrowed from prior practice. And incentives run against both: per-token pricing pays for volume rather than utility, and training rewards pleasing over precision. The principles hold where incentives and attention align; engineering discipline plus honest incentive design is the path.