Answers questions about a codebase: where something is implemented, what depends on what, how a flow works.
Retrieval and reasoning over a codebase, answering orientation questions that would otherwise require reading widely or interrupting someone.
Large codebases, onboarding, and cross-team work where nobody holds the whole picture.
Questions requiring certainty about all call sites. Retrieval-based answers are not exhaustive, and 'nothing else uses this' is a claim it cannot support.
Answers asserting completeness should be verified with static analysis rather than trusted, particularly before a deletion.
Confident incompleteness — describing three of five implementations of a pattern, with nothing indicating two were missed.
Asking which code paths write to the reconciliation status field before changing its state machine, then verifying the answer with static analysis.
Two different absences share this shape. Foundational solutions get built whatever the domain, so no domain links them; the rest are solutions this domain genuinely does not reach for. v_ai_solutions_unlinked separates the two.