Good information.
Traceable at every step.

What the collector reads.

The canonical statewide JSON supplies statewide and multicounty contest rows. All 100 county JSON feeds supply county detail and county-only contests. Local contest IDs are namespaced by county to prevent collisions. The election-night media ZIP supplies precinct-level voting-method records, including administrative precincts.

• Official results landing page
• Statewide contest JSON
• County reporting metadata
• Official election-night media ZIP
• Official historical and certified results archive

How missing choices are handled.

The November 4 audit found named choices present in the official media file but absent from JSON. The collector adds a missing choice only if every supplied JSON candidate’s party and all five vote counts match the media aggregation for the same county and contest. It preserves existing JSON counts. Aggregate supplements also require existing aggregate candidates to reconcile with county totals.

Supplemental rows are marked in results tables and exports. Exact source name variants remain separate. Percentages use the complete displayed candidate/choice sum. Derived aggregate and county supplements share the same media source; their equality is not an independent check. Read the dated audit →

When updates occur.

Official sources are checked hourly. The cloud collector sweeps 100 county files in three short batches; intermediate snapshots can contain county detail fetched at different moments. The interactive desk checks the cached collector every five minutes and briefly more often during a sweep. Reference pages reflect the collected snapshot shown above; use Refresh results to load a newer page.

What happens on a source failure.

Malformed, missing, negative, nonintegral, duplicate, or conflicting numeric rows reject the affected refresh. Last-good data remains visible with a delay notice. A mismatch between JSON and media prevents supplementation. A publication timing difference is not labeled a tabulation error.

What a source receipt proves.

A receipt records the official URL, fetch time, available HTTP timestamps, row count, and SHA-256 hash. JSON hashes identify fetched UTF-8 text; the media hash identifies ZIP archive bytes. A hash identifies a fetched publication; it is not a signature, certification, or independent verification of voting equipment.

What this site does not infer.

No race calls, estimated outstanding votes, candidate identity merges, recount eligibility decisions, automatic certification, or forecasts of legislative votes. A numerical majority and a veto-override threshold are different concepts; the latter depends on members present and voting.