constituency-ingest

name	constituency-ingest
description	Gather seat-level constituency information. Use when: updating one Kerala constituency inside the district coverage, review, and verification files with current-cycle supportability notes.

Constituency Ingest

When to Use

• Refreshing one constituency's live field
• Correcting one seat inside district coverage files
• Recording whether a seat is supportable, partial, or unsafe

Files

• public/data/constituencies.json
• research/constituency-coverage/<district>.md
• research/constituency-coverage-reviews/<district>-review.md
• research/constituency-coverage-verification/<district>-verification.md

Procedure

1. Find the seat's districtId in public/data/constituencies.json
2. Read the three district files for that district
3. Check Tier 1 and Tier 2 sources for the seat
4. Update only the matching seat section
5. State the strongest supportable field, confidence, and gaps

Guardrails

• Work one constituency at a time
• Do not force a full three-front slate when only one lane is source-locked
• If higher-tier and lower-tier sources conflict, mark the seat under_review or unsafe
• Keep exact source dates in the notes
• Never use constituency notes alone to publish product data

Handoff

• If one candidate becomes the clear front-runner, queue candidate-facts-ingest
• If the district is fully supportable, the publish step belongs to district-migration