Methodology

Every published event is traceable to a source, graded by evidence, and corrected in the open. Official announcement ≠ already in effect ≠ applies to all users.

Source grading

S1

Official sources

Official announcements, help centers, docs, status pages and official accounts. Direct official evidence.

S2

Official personnel

Public statements from vendor staff or official community support, verified for identity and context. Supporting evidence.

S3

Community

Reddit, Discord, Telegram and user reports. Used to discover leads and observe rollouts — never treated as official policy on its own.

Evidence levels

AOfficial ConfirmedDirect official evidence exists.
BCorroboratedMultiple reliable sources confirm each other.
CCommunity SignalCommunity reports; official policy not yet confirmed.
DUnverifiedInsufficient leads or questionable authenticity.

Evidence level and event status are two independent fields — an event can be “Official Confirmed + Rolling Out”.

Event lifecycle

Detected → Announced → Confirmed → Rolling Out → Observed → Expired, with Corrected and Retracted as auxiliary states. Announced means the vendor said it; Observed means we or reliable sources confirmed it actually applies.

DetectedAnnouncedConfirmedRolling OutObservedExpiredCorrectedRetracted

Editorial rules

  • Every published event has at least one source; important events always show evidence level and last verified time.
  • Unknown eligibility is marked as unknown — “not mentioned” is never interpreted as “applies to everyone”.
  • Community signals are labeled and never mixed into the officially confirmed stream.
  • Corrections and retractions keep full history; affected subscribers receive a correction alert.
  • We do not predict resets and we do not fabricate events to look busy. Empty means empty.
Methodology