How ResetPulse checks.
The goal is not to make the earliest possible claim. The goal is to surface a useful signal quickly, then make the confidence and limitations visible.
Collect
A server-side scheduler checks the monitored signal surface at a short, regular interval. Visitors do not need to keep a browser or computer running.
Normalize
Observed timestamps and content are normalized into a consistent event record so that days, time zones, and duplicate observations can be compared.
Verify
Detection and verification are separate states. A confirmed event requires matching author, timestamp, content, and reset scope rather than a single unexplained change.
Publish
The public timeline exposes the useful event history and the time of the last server-side check. Email alerts are sent only after a new event reaches the confirmed state.
How the faster lane works
The direct public page and a public timeline relay are requested concurrently. If one renderer is reachable while the other is delayed, the accepted event can still be observed earlier. This is a collection optimization, not extra evidence: both lanes are marked as the same-origin primary source, and neither is treated as independent corroboration.
Privacy by design
Public status responses remove private source URLs and internal identifiers. ResetPulse does not need your Codex credentials to show the public timeline. Email subscribers receive a confirmation step and can unsubscribe from every alert.
Read the live record
Return to the public reset timeline to see the latest checked status and historical events, or read the guide to interpreting reset signals.