How reset alerts work
Reset Beacon follows public Codex reset announcements and links each published event to its source. The status describes what has been announced and what has been confirmed.
Four kinds of update
Possible: a public post suggests a reset, with the relevant reply context where needed. It is not a promise or a confirmation.
Announced: a source promises a future reset. Any stated time or day comes from that source. Passing the scheduled reset time does not prove completion.
Confirmed: a public completion announcement states that the usage reset happened. The displayed timestamp is the announcement time, unless the source explicitly supplies a separate reset time.
Banked: a reset credit you can keep and redeem later. It is identified separately from an immediate usage reset.
Reading a post in context
A short reply may depend on the post it answers. We preserve that context and the source’s full captured words. An unrelated quoted post does not change a clear completion announcement into a different product or a forecast.
Public evidence
Published alerts use public source posts. Your own account’s Usage page is the authority on the allowance available to you. Normal five-hour and weekly plan windows are separate from shared reset announcements.
Times and fresh information
Public source checks run every five minutes.
Announcement times are saved as exact timestamps. The page and alerts show local times when your time zone is known; otherwise the time zone is stated. If current data is unavailable, the site says so rather than inventing a new event.
Corrections and records
A corrected or cancelled draft must pass review before its replacement is released. The history retains dated corrections. Historical forecast measurements remain on the track-record page; the current reset status does not show forecast percentages.