post-withdrawal-sweep

name	post-withdrawal-sweep
description	Reconcile live candidate rows against stronger post-withdrawal admin evidence. Use when: Form 7A, RO-office copies, Gazette notices, or other stronger final records are available and the statewide truth-refresh pass should deepen confidence.

Post-Withdrawal Sweep

When to Use

• When stronger post-withdrawal admin evidence exists for one district or the full state
• When updating live candidate facts from RO Form 7A, RO-office copies, Gazette publication, or comparable final records
• When starting the statewide truth-refresh pass before district precision work

Canonical Inputs

• research/statewide/admin-sources.md
• research/statewide/post-withdrawal-reconciliation-checklist.json
• research/statewide/post-withdrawal-reconciliation-checklist.md
• research/statewide/low-confidence-under-review-priority.json

Procedure

1. Read docs/INGESTION_OPERATING_MODEL.md and research/statewide/admin-sources.md
2. Refresh the target queue from research/statewide/low-confidence-under-review-priority.json (regenerate it from live district rows first if stale)
3. Use source-scout + evidence-landing agents to refresh admin evidence for targeted candidates
4. Reconcile candidate facts first using the admin stack: CEO hub, Form 7A / RO copy, Gazette, then RO/ARO escalation
5. Prefer direct admin proof for stronger status upgrades, but allow review-approved promotions from lower-tier evidence when source quality and wording stay explicit
6. If a row is already live and conservative, treat a negative admin sweep as a hold refresh only; do not demote published task/review/public state without direct contradictory proof
7. Trigger publication-agent for approved rows; run validation at wave closeout unless standards-keeper asks for tighter cadence
8. Do not partially renumber task-file constituencyNumber fields during candidate-local sweeps; keep task numbering stable unless a dedicated task-schema migration is in scope, while still aligning staged facts/timelines to the live district packet when that seat number is refreshed

Guardrails

• Do not update public/data/ first
• Do not restore removed rows without direct admin proof
• Do not treat "no stronger Form 7A / RO / Gazette proof found" as a reason to reopen an already-published conservative row
• Keep exact source dates and note whether the proof is Form 7A, RO-office copy, Gazette, or a lower-tier fallback
• Delay rich manual timeline expansion until the candidate row survives the admin pass

Handoff

• Follow statewide reconciliation with district precision in this order: Ernakulam, Malappuram, Palakkad, then weak high-browse seats in Thiruvananthapuram and Pathanamthitta
• Regenerate research/statewide/low-confidence-under-review-priority.json from live district rows after the sweep so the next pass starts from current truth