This Story Cannot Be Filed Without The OpenAI Post

This is a spike note, not a story. It is here so the decision is on the record rather than filed silently.

What was commissioned

A reported explanatory piece on a post published by OpenAI under the title "Apple is getting this wrong," concerning a legal dispute between OpenAI and Apple. The primary source was to be the post itself, at https://openai.com/index/apple-is-getting-this-wrong/.

Why it is not being filed

The post could not be retrieved. The assignment arrived with that already noted, and an attempt to fetch it during drafting failed as well — the tools that would reach the page are not available in this session. No text of the post is in hand: not the headline's argument, not the claims it makes, not the correspondence it reportedly reproduces.

What remains is a body of secondhand discussion among people reacting to the post. That material is background only under this publication's rules — it cannot be quoted, paraphrased, or attributed, and the venue it came from cannot be named. Those rules are not a formality. The people in it did not consent to publication, and they are not sources.

It is also not usable even as private guidance for assertion. It contains characterisations of documents its participants have not read, speculation about the contents of email attachments, claims about a named individual's conduct and his account hygiene, and an unrelated and entirely unverified allegation about a death. Every one of those is the kind of specific that, asserted in print about an active lawsuit between two very large companies, would need to be checked against a document. There is no document.

What would have been written, and why it would have been wrong

It would have been possible to produce something that reads like an article. The shape is available: a company litigating in public, a dispute over what an employee took with him, a partnership that soured. Prose can be confident about a subject it has not seen, and a reader has no way to tell the difference.

That is precisely the objection. An explanatory piece earns its authority by walking a reader through a chain of reasoning where each step can be checked. If the first link — what the post actually says — is supplied by inference rather than by reading, then everything downstream is decoration on a guess, and the reader is being asked to trust a chain that was never verified end to end. Filing that would spend credibility this publication needs for the stories it can support.

What unblocks it

Any of the following makes the piece writable:

• Access to fetch the OpenAI post directly.
• The full text of the post, supplied in the assignment.
• Coverage from an established outlet reporting on the post, together with permission to cite and link it — the current brief permits only the one OpenAI URL, which is the URL that cannot be reached.

The underlying question is a good one and worth returning to. A company choosing to argue an active case on its own blog, rather than only in filings, is making a deliberate trade: it accepts the risk that anything it publishes becomes evidence, in exchange for shaping how the dispute is understood before a court ever rules. Explaining why a company would take that trade, and what it suggests about what it thinks is at stake, is a real story.

It is a story that requires reading what was actually published.