Reading a press release for the sentence that is missing

A press release is a document written by people who want you to be excited. The skill in reading one is in noticing what it does not say, and in noticing where it changes the subject.

Three omissions recur in AI announcements, and they are the same every time.

The comparison that is absent. A launch that follows a rival’s will often avoid naming it. When OpenAI introduced Dots in September 2026, the announcement described always-on agents with their own cloud computers, and it never once named Meta’s Muse, which Meta had announced on September 8, three weeks earlier, with a similar design: a dedicated virtual machine, a browser, background work, and approval before sensitive actions. The absence is the story.

The scope that stays vague. The Dots announcement says the first dot is included at no extra cost. Later it says that in the future you can add more dots and scale each one’s speed or monthly work, and the page gives no price or limit for either. The first sentence is precise and reassuring. The second is precise about the fact that more will cost, and vague about how much. The change in specificity between the two paragraphs is where the real information lives.

The caveat that lives one click away. The announcement says dots are rolling out to Pro and Business Premium users in eligible markets, and the list of markets sits behind a link. The Help Center page adds that Pro excludes the European Economic Area, Switzerland, and the United Kingdom at launch, and that the rollout is gradual. The fine print lives one click away, and the release would rather you be excited first and patient second.

These omissions are ordinary advertising practice. A press release is an advertisement, and an advertisement is not required to volunteer its weaknesses. The omissions still matter, because they show you where to look for what the company chose not to say.

Here is how to read one.

Read it twice, in different orders. The first time, read top to bottom the way the author intended, to understand the pitch. The second time, read bottom to top, so the caveats hit you before the enthusiasm does.

Underline every number, then ask what it is missing. A benchmark score without the tested version. A speedup without the hardware. A price without the conditions. A number that arrives without its comparison is a number you cannot use.

Look for the sentence the release is avoiding. If a rival launched recently, ask whether the release names it. If a feature is described as included, ask what is not included. If an availability date is given, ask which regions and plans are excluded.

Watch the verbs. “Will support,” “plans to,” “rolling out,” and “coming soon” are not the same as “available now.” A release that uses the future tense for the thing you care about is telling you that thing is not ready.

None of this means the product is bad. Meta’s Muse and OpenAI’s Dots are both real, large, multi-part systems. Reading a release closely lets you know, before you get excited or make a decision, which sentences are facts and which are plans, which numbers are complete and which are missing their other half, and which rival’s name is being held off the page.

The sentence that is missing is often the most useful one in the document. Go looking for it.