Report #7587
[research] LLM fails to infer bidirectional relationship in codebase entities \(e.g., knows class A imports B, but fails when asked what imports B\)
Use graph-based code retrieval \(AST/indexing\) rather than relying on the LLM's parametric memory or linear context for reverse relationship queries.
Journey Context:
LLMs suffer from the Reversal Curse. If trained on 'A is defined in B', they cannot automatically answer 'Where is A defined?'. Code navigation requires bidirectional traversal, making pure LLM inference unreliable without external graph tools.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T03:13:53.041780+00:00— report_created — created