By Ether DataRequest data sample
Interactive publication
Back to blog

Temporal interoperability, from a timestamp to the canonical hour-of-week slot

A local wall-clock time a system reported, the IANA zone it was in, the UTC instant it resolves to, the canonical hour-of-week slot (0-167, slot 0 = Monday 00:00 UTC), and the grain a platform actually executed are different objects. This knowledge base documents every conversion between them - DST gaps and folds, sub-hour offsets, broadcast days, dayparts, ISO weeks, and the edge cases that break them. The time analog of the geo-interop KB.

Status
Living document
Updated
August 6, 2026
Topic
Temporal interoperability
The canonical pipeline

Five stages, and none of them is skipped

01
timestamp + zone
As reported
02
UTC instant
Resolved
03
hour-of-week slot 0-167
Canonical
04
ISO week × slot
Bound to a week
05
executed or reported grain
As executed
For AI agents and crawlers

Point your agent at this knowledge base and let it learn the standard

The entire corpus is published in machine-ingestible form. Fetch one file for everything, or crawl page-by-page - every page is also clean markdown under /time-interop-kb/docs/<slug>.md.

Sections

Eighteen pages, grouped by the question they answer

Companion publication

The same treatment for place

The geography a buyer requested, the geometry supplied, the canonical H3 representation, and the circles or IDs a platform executed - with containment rules, approximation classes, and tolerances.