Files
ietf-draft-analyzer/workspace/draft-team/references/analyzer-integration.md
Christian Nennemann 2506b6325a
Some checks failed
CI / test (3.11) (push) Failing after 1m37s
CI / test (3.12) (push) Failing after 57s
feat: add draft data, gap analysis report, and workspace config
2026-04-06 18:47:15 +02:00

1.3 KiB

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.