timeline-batch-enrichment

name: timeline-batch-enrichment description: 'Refresh generated candidate timeline seeds and deepen staged timelines in bulk. Use when: reseeding statewide timeline minima, enriching one priority seat cluster, or syncing public candidate timelines after staged event work.'

Timeline Batch Enrichment

When to Use

• Refreshing research/candidate-timeline-seeds/ for live-app-linked candidates
• Deepening staged timelines for one priority seat or district cluster
• Projecting staged timeline updates into public candidate dossiers

Canonical Outputs

• research/candidate-timeline-seeds/<candidateId>.json
• research/candidate-timelines/<candidateId>.json
• public/data/candidate-details/<detailId>.json

Procedure

1. Read docs/INGESTION_OPERATING_MODEL.md
2. Trigger facts/timeline agents for the target candidate or priority seat cluster
3. Keep generated events stable by preserving eventId; suppress instead of deleting when an item should stay hidden
4. Trigger publication-agent for approved candidates
5. Trigger ingestion-validator-agent

Guardrails

• Do not edit public/data/ first
• Do not remove manual timeline events just because a generated seed changed
• Do not publish current-cycle definitive status above the evidence tier allowed in docs/INGESTION_OPERATING_MODEL.md
• If a candidate facts row is withheld, keep generated current-cycle events suppressed

Handoff

• If the seed contract or merge rules change, update the ingestion docs, repo docs, and handoff notes in the same session