Source policy
Every source has a boundary.
An official schedule can establish intent and timing. Only a completion statement or an account-level change can establish that a reset happened.
| Priority | Source | What it establishes |
|---|---|---|
| Very high | Official explicit time and clarification | The intended date, hour and source wording for a scheduled window. |
| Very high | Official completion statement | The reset action was said to be triggered; propagation may remain incomplete. |
| Very high | Fresh account usage or status reading | The strongest proof that one account’s allowance changed. |
| High | Multiple independent paid-account reports | Whether rollout has begun across plans and coarse regions. |
| Context | Historical events and incident context | A prior probability, not a current commitment. |
| Advisory | Independent trackers | Discovery and archives; never official confirmation authority. |
| Unverified | Reposts, anonymous predictions and single reports | At most an investigation lead. |
Primary references
Official sources come first.
Correction policy
Changes stay attached to the event.
If a source corrects an hour, date or timezone, the forecast updates and the prior interpretation remains in the event record. Subscribers who received the affected alert receive a correction without waiting for the normal quiet period.
Deleted posts are never paraphrased as live official evidence without an archive that preserves the original identifier and timestamp. Mirrors help recover context, but are labeled as mirrors.
If the scheduled window passes without adequate completion evidence, the state changes to “Window passed, unconfirmed.” It does not silently roll forward.