Geographic interoperability, from source geometry to executable platform geography
The geography a buyer requested, the geometry that was supplied, the canonical H3 representation, the circles or IDs a platform actually executed, and the geography used for reporting are usually five different objects. This knowledge base documents every conversion between them - with containment rules, approximation classes, units, tolerances, and the edge cases that break them.
Five geographies, and none of them is a stand-in for another
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 /geo-interop-kb/docs/<slug>.md.
Fifty-one pages, grouped by the question they answer
The same treatment for time
A timestamp and its zone, the UTC instant it resolves to, the canonical hour-of-week slot, and the grain a platform executed - with DST gaps and folds, broadcast days, dayparts, and ISO weeks.