Run any Skill in Manus with one click

post-withdrawal-sweep

Stars1

Forks0

UpdatedMarch 27, 2026 at 15:46

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aarshps

aarshps/hora-prathinidhi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Court, Municipal, and License ClerksOffice and Administrative Support Occupations·SOC 43-4031

SKILL.md

readonly

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

Read docs/INGESTION_OPERATING_MODEL.md and research/statewide/admin-sources.md
Refresh the target queue from research/statewide/low-confidence-under-review-priority.json (regenerate it from live district rows first if stale)
Use source-scout + evidence-landing agents to refresh admin evidence for targeted candidates
Reconcile candidate facts first using the admin stack: CEO hub, Form 7A / RO copy, Gazette, then RO/ARO escalation
Prefer direct admin proof for stronger status upgrades, but allow review-approved promotions from lower-tier evidence when source quality and wording stay explicit
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
Trigger publication-agent for approved rows; run validation at wave closeout unless standards-keeper asks for tighter cadence
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

More from this repository

same repository

data-validation

aarshps/hora-prathinidhi

Validate integrity of all public/data JSON files. Use when: after editing candidates, constituencies, or districts JSON; before committing data changes; checking coverage completeness; debugging data mismatches.

2026-04-251

public-candidate-sync

aarshps/hora-prathinidhi

Refresh public district candidate rows from structured live-field research plus staged facts/timelines. Use when: surfacing all candidates per constituency in the app, resyncing public/data after research candidate changes, or restoring legacy candidate route aliases.

2026-04-251

session-wrap-up

aarshps/hora-prathinidhi

Wrap up a meaningful repo work session. Use when: folding durable learnings into repo-local skills, syncing AGENTS/README/handoff docs, or preparing the final close-out commit and push.

2026-04-241

issue-watch-closeout

aarshps/hora-prathinidhi

Drive recurring GitHub issue work from shipped slices to final closeout or reusable closed-issue audits.

2026-04-241

constituency-outcome-slice

aarshps/hora-prathinidhi

Work one bounded constituency possible-outcome slice. Use when: creating or reviewing seat-local outcome packets under the new 1 primary + 3 reviewer workflow.

2026-04-081

ui-conventions

aarshps/hora-prathinidhi

UI rules for the Kerala elections app. Use when: modifying components, adding status indicators, changing how candidates or constituencies display, or touching motion.

2026-04-071

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

Read docs/INGESTION_OPERATING_MODEL.md and research/statewide/admin-sources.md
Refresh the target queue from research/statewide/low-confidence-under-review-priority.json (regenerate it from live district rows first if stale)
Use source-scout + evidence-landing agents to refresh admin evidence for targeted candidates
Reconcile candidate facts first using the admin stack: CEO hub, Form 7A / RO copy, Gazette, then RO/ARO escalation
Prefer direct admin proof for stronger status upgrades, but allow review-approved promotions from lower-tier evidence when source quality and wording stay explicit
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
Trigger publication-agent for approved rows; run validation at wave closeout unless standards-keeper asks for tighter cadence
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