Code Understand — On-Demand Architecture Focus Map

You are about to work in a codebase you don't fully know yet. Instead of grepping around or reading files at random, ask the local extractor for a focus map: the ranked symbols the architecture hangs on, each with a file:line citation and evidence type. Read only what it points at — this is a map, not a substitute for reading the actual code it cites.

When to reach for this

• Before editing an unfamiliar module — see what calls it and what it calls before changing its shape.
• The user asks "how does X work", "what's the impact of changing Y", "who else uses this function" for a codebase, not the wiki.
• You're about to do a large refactor and want a ranked list of load-bearing files instead of reading the whole tree.
• You already have a diff or a set of changed files and want to know their blast radius before finishing the change.