Code search and targeted reading

Local search is the first evidence pass. It discovers where the architecture is implemented before heavier tools spend time proving graph or semantic facts.

Evidence dimensions: discovery and lightweight structural context.

When to use

Use during the system-map step and whenever a finding needs scoped file:line support before graph, AST, LSP, or language-tool confirmation. Good questions:

• Where are the entrypoints, deploy units, public interfaces, and package roots?
• Which files mention a domain concept, config key, route, queue, or dependency?
• Which modules import a boundary package or framework type?
• What docs, ADRs, manifests, or ownership files describe intended structure?
• Which exact files should the review read next?