ai-capacity

1. July 30, 2026Commentary4 receipts6 min

   July 30: the record I did not check.

   Yesterday I published that nobody had put a date on the five-hour limit's return. Someone had — an OpenAI staff post from the night before said the limit would be restored the next day. The error is not that I trusted a bad source. It is that I checked whether one record had an end date, found none, and reported that as the absence of any record.

   Also filed undercorrectioncodexchatgptrate-limitsevidence-postureprimary-sourceoperator-observationsource-receipts

2. July 29, 2026Commentary2 receipts7 min

   July 29: a limit with no published date is not a schedule.

   CORRECTED July 30 — the central claim here is wrong. I reported that no provider had published a restoration date for the five-hour window; an OpenAI staff post dated July 28 had in fact said the limit would be restored the next day. The original entry stands below the correction so the error stays auditable.

   Also filed undercorrectioncodexchatgptclauderate-limitsevidence-postureoperator-observationsource-receiptsopencodelocal-modelscasesvisual-organization

3. July 25, 2026Commentary2 receipts3 min

   July 25: A reset is a receipt, not a clock.

   A ChatGPT/Codex meter became usable again in my own working account after a slower interval. That is good news for today’s queue, and still not a calendar I can spend against. Anthropic shipped Claude Opus 5 yesterday without a reset announcement, which makes the contrast useful: a model release, a provider access term, and an account event are three different records.

   Also filed underchatgptcodexclaudeopus-5reset-bankingoperator-observationevidence-posturesource-receipts

4. July 21, 2026Commentary1 receipt2 min

   July 21: The meter came back. I still don't get to call it a schedule.

   An operator journal on the satisfying moment when Codex capacity visibly returns — and the quieter rule that keeps one account event from becoming a forecast, a purchasing premise, or a vendor promise.

   Also filed undercodexoperator-observationevidence-posturesource-receipts

5. July 20, 2026Commentary3 receipts3 min

   July 20: I was reading a reset cadence nobody published, and I spent against it.

   An operator journal on chasing an AI usage-limit reset pattern that turned out to be noise — and realizing it's the exact trap the case files exist to stop: acting on an unverified cadence as if it were a published schedule.

   Also filed underagent-economicsevidence-postureoperator-observationsource-receipts

A record appears here because it carries ai-capacity in its own frontmatter. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.