“Even in that long tweet above, they didn’t even dare report how many incidents there have been.”
Our reading, the sentence that was checked:
OpenAI's long tweet did not report how many incidents there had been.
Assessment: Supported Evidence as of
Where and when Gary Marcus wrote it
Marcus on AI, BREAKING: OpenAI’s epic meltdown — and how Sam Altman is blowing up Jensen Huang’s reputation, paragraph 13.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment marcus-breaking-openais-security-fiasco-1f539f-a1
We recorded 12 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2026-09-25. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Observation
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No horizon
- Deadline state on 2026-10-29
- No horizon (the release’s reference date)
Conditions
- in that long tweet (scope, stated by the speaker)
From the speaker
- in that long tweet
- didn’t even dare report
- how many incidents there have been
Our interpretation
- The object is the complete OpenAI post beginning with its commitment to review activity after the Hugging Face incident.
- The checkable assertion is the absence of an incident count. The phrase about daring to report imputes a motive that the text alone cannot establish.
- A count of organizations, impressions, or individual actions would not automatically constitute an incident count.
Counts as supported if: The complete identified post contains no numerical incident total or numerical estimate of that total.
Counts as contradicted if: The identified post explicitly reports a total or numerical estimate of incidents.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Was it true for the period described?
Outcome: Supported
The dated evidence matches what the claim committed to, under the criteria frozen before grading.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No horizon
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
The complete identified post gives no incident total or numerical estimate. Its qualitative statements about the majority of reviewed activity do not provide a count. The omission is verified; Marcus’s suggestion about why OpenAI omitted it is not.
Limitations
- This finding concerns the post itself, not whether counts appeared elsewhere.
- No conclusion is drawn about OpenAI’s motive.
Evidence (1 item)
Supports the claim: OpenAI,
ongoing.
Why it matters here: The complete post discusses the review, general severity, notifications, and expected duration. It contains no incident count; the quoted sentence is an anchor to the inspected document, not by itself proof of an omission.
- Publisher
- OpenAI
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
Where it was said (1)
Said once in the sources this register covers.
: Marcus on AI, BREAKING: OpenAI’s epic meltdown — and how Sam Altman is blowing up Jensen Huang’s reputation
Even in that long tweet above, they didn’t even dare report how many incidents there have been.
- Where
- paragraph 13
- Published
- 2026-09-25
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment marcus-breaking-openais-security-fiasco-1f539f-a1: Current. Outcome: Supported. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
About assessment marcus-breaking-openais-security-fiasco-1f539f-a1.