Version mismatch between execution and reporting

temporal

The H3/boundary/crosswalk version active at campaign execution time can differ from the version active when the reporting/measurement query runs later, causing the same nominal geography to resolve to different actual cells between planning and results.

Detection

Compare the crosswalk/boundary version identifier stamped at execution time against the version currently active when reporting queries run; flag any difference.

Mitigation

Pin and log the exact crosswalk/boundary version used at execution time in the campaign record
Always run reporting/measurement joins against the pinned execution-time version, never the current-latest version

Affected conversions

Admin polygons → H3 (weighted crosswalk) weighted
H3 → platform-native IDs approximate
Cell system → cell system approximate