Zooming Out on Code

Boundary

Orient one level above the requested symbol, file, module, or package. This is read-only analysis. Do not modify files, recommend refactors, identify architecture candidates, debug a defect, or propose next steps.

If CONTEXT.md or relevant ADRs exist, read them as vocabulary and decision evidence only. Never create or update them. When they are absent, infer terms from package names, public types, tests, and callers and record uncertainty.

Process

1. Identify the containing unit one level above the requested target.
2. State its single domain responsibility from observable code and tests.
3. Find direct callers through exports, imports, references, routes, or configuration.
4. Read direct dependencies only; do not expand transitive graphs.
5. List siblings in the same package or layer and their distinct responsibilities.
6. Separate unresolved or conflicting evidence into Unknowns.
7. Stop after the five-field map.

Prefer symbol-aware references when available, then targeted text search. Search re-exports if direct callers appear empty. Cite concrete paths; distinguish evidence from inference.