research-intelligencelisted

# research-intelligence ## Overview Three stages: **Planner → Router → Synthesizer.** This file stays thin on purpose — sub-skills load only when actually dispatched, so a quick single-source request never pulls in the whole pipeline's token cost. See ../../ARCHITECTURE.md for the 13 locked rules everything below implements; this file doesn't restate them. ## Stage 1 — Planner Invoke `research-planner`. It decomposes the question into sub-questions, matches each to source skills, sets a search budget, and sets the stopping condition. **For anything beyond `quick-research`, it confirms the drafted scope with the user before dispatch** — a full pipeline can touch most of the 8 source skills and take a long time, and that's the cheap point to narrow it. Its output is a user-confirmed plan, written to the run's ledger — not evidence. ## Stage 2 — Router Dispatch the source skills the plan calls for: `web-research`, `github-research`, `reddit-research`, `blog-research`, `news-research`, `academic-research`, `official-source-research`, `social-research`. Invoke by name — never inline a source skill's procedure here; each loads only when actually needed for this run. Each source skill writes `evidence.jsonl` records with `verification_status: pending`. When the plan's stopping condition is met (constitution rule 11: every sub-question meets its bar, or 2 consecutive rounds with no new evidence), collection ends for that run. Then invoke `source-verify` on the full pending se