| name | timeline-review-checker |
| description | Optional helper for one candidate review pass in the active worker-pool model. |
Timeline Review Checker
When to Use
- Running an explicit second-pass review when the end-to-end worker is split into helpers
- Evaluating staged facts and timeline claims against all guardrails
- Writing canonical review JSON for a candidate already inside the active
queued -> assigned -> published | blocked workflow
Canonical Output
research/swarm/reviews/<candidateId>.json
research/swarm/tasks/<candidateId>.json (publication handoff or blocked state)
research/swarm/escalations/state.json when blocked
Procedure
- Read
research/swarm/guardrails.json and the candidate task before acting
- Confirm the candidate is claimed in the owning shard's
activeAssignments
- Independently verify timeline and facts: source tier, eventStatus ceiling, date validity, no duplicate eventId, no overclaiming, no unsupported reword-only strengthening, no affidavit/declaration microcard spam, and no facts/timeline conflicts
- Write canonical review JSON with the active worker-pool metadata the repo already uses
- Apply the decision in task file as a publish handoff or blocked stop; if policy-blocked, update the rolling entry in
research/swarm/escalations/state.json
Defect Codes
BAD_SOURCE_TIER · PRE_WITHDRAWAL_OVERCLAIM · TIMELINE_RULE_VIOLATION · FACTS_SCHEMA_DRIFT · PROVENANCE_DRIFT · LEGACY_SURFACE_WRITE · MISSING_EXACT_DATE · NON_VOTER_USEFUL_EVENT · DUPLICATE_ASSIGNMENT · BATCH_RULE_VIOLATION · PUBLIC_COPY_LIMIT · OVERSTATED_REWORD · DECLARATION_SPAM
Guardrails
- Do not edit candidate facts or timelines
- Do not write review prose outside the JSON payload
- Task file is authoritative under contention
- Do not create run-numbered escalation artifacts
- This helper is optional; the default end-to-end worker may write its own review JSON before publication
Handoff
- Approved -> publication by the same worker or orchestrator follow-up; rejected/blocked -> orchestrator follow-up