// GEO & Query Semantics
How geographic identity and query semantics work across products, with geo_object_id as the primary contract key.
geo_object_id is the primary contract key across region-facing surfaces and should be preferred over legacy compatibility patterns.
Use geo_object_id as the default join key across region-facing outputs.
Do not assume every endpoint accepts the same secondary filters.
Treat compatibility aliases as transitional rather than primary contract forms.
Facilities, news, events, and profile all share geo identity, but they do not share identical freshness or coverage semantics.
Use the same geo contract key, but read each surface according to its own delivery boundary: facilities as normalized records, news as the current live baseline, events as recent non-empty aggregates, and profile as synthesized context.
Integrations should be built against product-specific semantics rather than assuming every region-facing endpoint behaves like a raw geo feed.