Sources & countdown method

We mirror the public Codex RSS from whenreset.dev, which describes its own process as periodic collection and human review. We do not independently monitor X or verify account refills.

Synchronization

Page and API requests trigger a refresh when the stored attempt is at least five minutes old. Open visible pages check every five minutes. A database claim prevents simultaneous visitors from duplicating upstream requests. No always-on scheduler is configured.

Announcement interpretation

Relative durations such as “in 75 minutes” are calculated from the source post’s publication time, never from our fetch time. Approximate wording remains labeled approximate. Ambiguous local clock times, missing timezones and “end of day” wording do not create a precise countdown.

Only an explicit subsequent completion report changes a pending announcement to reported completion. A timer reaching zero is not evidence of a refill. Banked grants are kept separate from global usage resets. No historical forecast probability or next-date estimate is published.

Source failures

Fetch errors retain the last successful snapshot with a warning. A successful fetch tells us we read the upstream feed, not that the upstream continuously observed every original post.