Populace is moving to a single national US H5 with state/CD scoping columns instead of publishing one file per state or congressional district. policyengine.py still has release/provenance surfaces that assume regional artifact path templates such as states/{state_code}.h5 and districts/{district_code}.h5 in certification tests, fixtures, and bundled country metadata.\n\nMigration target:\n\n- US regions should resolve to the single certified Populace dataset plus a scoping strategy, not regional dataset paths.\n- Certification/provenance should reject or ignore states/*.h5 and districts/*.h5 for Populace releases once the single-H5 contract is active.\n- Keep historical bundle snapshots readable if needed, but do not require new Populace releases to publish regional artifacts.
Populace is moving to a single national US H5 with state/CD scoping columns instead of publishing one file per state or congressional district. policyengine.py still has release/provenance surfaces that assume regional artifact path templates such as
states/{state_code}.h5anddistricts/{district_code}.h5in certification tests, fixtures, and bundled country metadata.\n\nMigration target:\n\n- US regions should resolve to the single certified Populace dataset plus a scoping strategy, not regional dataset paths.\n- Certification/provenance should reject or ignorestates/*.h5anddistricts/*.h5for Populace releases once the single-H5 contract is active.\n- Keep historical bundle snapshots readable if needed, but do not require new Populace releases to publish regional artifacts.