# Analyzer Integration

Use `/home/c/projects/ietf-draft-analyzer` as the primary evidence source unless the user overrides it.

## High-value inputs

- `README.md`: current project scope and headline findings
- `data/reports/gaps.md`: strongest starting point for candidate draft topics
- `data/reports/ideas.md`: extracted ideas and recurring mechanisms
- `data/reports/overview.md`: broad landscape summary
- `data/reports/overlap-clusters.md`: duplication and collision risk
- `data/reports/holistic-agent-ecosystem-draft-outlines.md`: idea seeds that may already exist
- `data/reports/draft-*.md`: focused analysis for specific candidate drafts
- `paper/main.tex`: current publication framing and terminology

## Suggested evidence order

1. read the relevant cycle files
2. read `gaps.md`
3. read one or two supporting reports
4. read individual draft reports only when needed
5. inspect source code or DB only when the reports are insufficient

## Research heuristics

- If the gap is already heavily covered, shift toward comparison or refinement instead of greenfield drafting.
- If the gap touches trust, security, provenance, or rollback, inspect adjacent categories to avoid missing overlapping work.
- If the user asks for a publishable draft, verify the proposed scope is small enough to defend in one document.
