The first edges in the repo. Every US county now links to the districts it
sits in, weighted by area overlap, and every legislator links to the district
they represent — county → district → representative, traversable.
Data (PostGIS, no Atlas dependency — computed directly from geometry):
- data/county_district_edges.jsonl — 16,328 weighted edges. area_weight =
ST_Area(ST_Intersection(county, district))/ST_Area(county) over ST_MakeValid
Census TIGER 2024 geometries, overlaps <0.5% dropped. Uses area-intersection,
NOT centroid-in-polygon, so urban districts that carve through counties
(e.g. GA CD-5 / Atlanta across Clayton+DeKalb+Fulton) are captured, not
silently dropped. Per-county weights sum to ~1.0 per district type.
build.py:
- ~6,896 new district nodes: 435 CD (ACS demographics where available; sparse
for the 8 states missing from acs_cd) + 4,927 state-house + 1,897 state-senate
(geometry-only). GEOID/number-keyed, stable.
- county index.md gains a `districts:` block (frontmatter) + a ## Districts
section (body links, so link-integrity checks them).
- legislators + US House members gain `represents:` pointing at their district
node; edge stored once on the person, inverse left to the view.
- schemas/jurisdiction: classification enum + chamber/districts fields.
Honest gaps (logged, not hidden): ID + NH have no state-house geometry, so
their house districts get nodes (represents resolves) but no county edges;
CD nodes for acs_cd-missing states are demographically sparse.
Deterministic (byte-identical rebuild); validate.py passes 26,617 records,
link-integrity clean (every district/represents link resolves).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The README claimed 'validated by JSON Schema' — now it is true.
/schemas holds a JSON Schema for each entity type (Person, Body,
Candidate, Jurisdiction): a stricter profile over OKF's permissive
base, tolerating unknown keys by design.
scripts/validate.py checks all 17,506 files with no third-party deps
(hand-rolled frontmatter parser + minimal schema engine):
1. OKF conformance — every file has frontmatter with a non-empty type
2. Schema conformance — required fields, property types, enums
3. Link integrity — internal /-rooted links resolve
Non-zero exit on failure, so it is a CI gate. Verified with a negative
test: it catches bad enums and dead links. All 17,506 files pass today.
Makefile ties it together: make build / validate / check.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Fabio