Trace Citations
Map the citation graph around one focal paper into useful buckets. Use this when the human wants lineage, influence, and strong versus weak citation edges around a paper.
Arguments
- The positional argument is the focal paper query. Quote multi-word titles.
--depth 1|2controls whether to expand a second hop from the strongest first-hop edges.--max-references <n>and--max-citations <n>cap the first-hop fetch sizes.--second-hop-limit <n>caps how many first-hop anchors get expanded at depth two.
Workflow
- Run
python scripts/run.py .... - Read
result.foundationsfor strong references behind the focal paper. - Read
result.direct_descendantsfor strong citing descendants. - Read
result.bridge_nodesfor medium-confidence connectors with rich context or intent signal. - Read
result.weak_edgesfor low-signal edges that are probably less useful. - If
depth=2, readresult.second_hoponly after the first-hop picture looks sensible.
Output
- The script prints the unified JSON envelope described in
output_contract.md. - The underlying workflow result is
CitationTraceResult.to_dict(). result.reference_count_examinedandresult.citation_count_examinedshow the first-hop search breadth.
When To Escalate
- The focal paper resolves incorrectly.
- The API returns very sparse context and intent data, making edge interpretation weak.
- The first-hop graph is too noisy and needs a tighter focal paper choice before going to depth two.