Pundit ClaimsAI claims by Gary Marcus and Ed Zitron, with the evidence

“A Claude Code or OpenAI Codex user cannot with any clarity say that in three months their current workload or workflow will be possible based on their current subscription.”

The Subprime AI Crisis Is Here, paragraph 177.

Our reading:

Claude Code and Codex subscribers cannot know whether their current workloads will still be supported in three months.

Assessment: Supported

What happened

Was it true for the period described?

Outcome: Supported

The evidence matches what they said.

Judged on a plain reading. They named no measure, so we used the reading a typical informed reader would take. It is spelled out under “How we judged it”.

Evidence up to . Checked .

Why

Anthropic's standard terms in force on March 31, 2026 allowed feature changes and capacity reductions, subject to separately agreed terms [e1]. OpenAI's terms in force that day allowed service changes and required at least 30 days' notice for materially adverse changes to the terms [e2]. These provisions supplied no three-month assurance that an ordinary subscriber's existing workload would remain supported unchanged through June 30, 2026 [e1, e2].

Caveats

  • The terms do not establish practical predictability for any particular workload or whether it later became unsupported [e1, e2].
  • The cited standard terms do not establish the protections in separately negotiated agreements [e1, e2].

Evidence (2 items)

  • Supports the claim: Anthropic,

    decrease capacity limits

    Why it matters: The terms effective before publication expressly permit changes to features and capacity. Their application on the post date supports the absence of a standard three-month assurance; separately agreed terms are an explicit exception.

    Publisher
    Anthropic
    Kind of source
    Company disclosure: the company describing itself, not an independent finding
    About events on
    Published
  • Supports the claim: OpenAI,

    our Services

    Why it matters: The individual-service terms permit service changes and provide 30 days' notice for materially adverse changes to the terms. That protection is not a three-month commitment to preserve a particular workload.

    Publisher
    OpenAI
    Kind of source
    Company disclosure: the company describing itself, not an independent finding
    About events on
    Published

How we judged it

Kind of claim
Observation
Deadline
None given. We don’t add one.

Where we had to interpret

  • The ordinary reading concerns reliable assurance supplied by a standard subscription, rather than a prediction that every user's workflow will actually fail.
  • Assess the terms in force on March 31, 2026, and whether they assure unchanged workload support through June 30, 2026.
  • The scope is ordinary individual subscriptions. Separately negotiated enterprise guarantees require separate examination.
  • Three months describes the assurance being discussed; it does not turn the statement into a forecast of actual service failure.

Right if: Both providers' standard terms allow relevant service or capacity changes within three months and do not assure unchanged support for a subscriber's existing workload throughout that interval.

Wrong if: The relevant standard subscriptions provide enforceable three-month assurances of the capacity and functionality needed to continue existing workloads.

We wrote this test after the outcome was known.

We found 54 claims in this post. See them all.

Full record

Source and dates

Where's Your Ed At, The Subprime AI Crisis Is Here, paragraph 177.

Said
We read the source
live page, full text, public
Evidence up to
Checked

We read this wording on 2026-10-28. The post may have been edited after 2026-03-31.

Where it was said (1)

Said once in the posts we read.

  • : Where's Your Ed At, The Subprime AI Crisis Is Here

    A Claude Code or OpenAI Codex user cannot with any clarity say that in three months their current workload or workflow will be possible based on their current subscription.

    Published
    2026-03-31
    We read it
    , live page
    Access
    full text, public

History

Versions

  • Current: Supported. Evidence up to 2026-10-28.

What happened to this record

  1. PublishedBy us

    Published after both AI reviews and the final check passed.

  2. Held backBy us

    The final check failed: the write-up said more than the evidence showed.