Editorial Policy
How Clockjumper decides what to publish, how facts are checked, and who is responsible for the result.
Time-zone data
Every offset, DST transition, and abbreviation on the site is computed at render time from the IANA tz database via the browser and server's Intl APIs. Nothing is hardcoded. When the tz database updates (leap seconds, DST-rule changes, new zones), the site inherits the change on the next deploy without an editorial edit.
Event schedules
Every event carries a verification_status field with one of four values:
- speculative — expected month only, no precise date-time, no countdown,
noindex. - provisional — a date exists but has not been cross-checked against an official source. Noindexed and shown without a precise countdown until verified.
- official — verified against a named source URL and a dated
last_verified_at. Only official events are indexed, carry a precise countdown, and expose an AddToCalendar action. - completed — the event has finished; kept as a historical record.
The "Verified — source" line on every event page links back to this policy so the provenance claim is traceable.
Research
The Workday Overlap studies are derived from a registry-defined city list using four transparent selection gates and a single reproducible overlap engine. See the research methodology for the exact rules and the linked dataset for the underlying rows.
Corrections
Every substantive fix is logged with a date on the corrections page. Reach out via the contact address on About to report an error.
Editorial responsibility
The named editor and reviewer responsible for Clockjumper's published content is Perry — Editor, Clockjumper. All research studies and event verifications are reviewed by the editor before an "official" status is applied.