evidence-binder

# Evidence Binder (NO PROSE) Goal: convert a paper-level pool into a **subsection-addressable evidence plan**. This skill is the bridge from “Evidence Bank” → “Writer”: the writer should only use evidence IDs bound to the current subsection. Why this matters for writing quality: - Weak/undifferentiated bindings force the writer to either pad prose or cite out-of-scope. - Treat `binding_gaps` as a routing signal: fix upstream evidence/mapping instead of "writing around" missing evidence. ## Inputs - `outline/subsection_briefs.jsonl` - `outline/mapping.tsv` - `papers/evidence_bank.jsonl` - Optional: - `citations/ref.bib` (to validate cite keys when evidence items carry citations) ## Outputs - `outline/evidence_bindings.jsonl` (1 JSONL record per subsection) - `outline/evidence_binding_report.md` (summary; bullets + small tables) - Includes `gaps` (missing required evidence fields) and `tag mix` (selected evidence tags) so subsection-specific evidence needs are visible. ## Output format (`outline/evidence_bindings.jsonl`) JSONL (one object per H3 subsection). Best-effort fields (keep deterministic): - `sub_id`, `title` - `paper_ids` (papers in-scope for this subsection, from `mapping.tsv`) - `mapped_bibkeys` (bibkeys mapped to this subsection) - `bibkeys` (a selected subset to encourage subsection-first citations) - `evidence_ids` (selected evidence items from `papers/evidence_bank.jsonl`) - `evidence_counts` (small summary by claim_type / tag / evidence_level) - `...