Question
Who owns this behavior, what does that module depend on, and who depends on it?
Recipe
loct repo-view
loct hotspots --limit 8 --coupling
loct tagmap authentication --include-tests --limit 6
loct focus src/auth --depth 1
loct slice src/auth/session.rs --depth 1
Use your own domain term and paths. tagmap discovers a domain across code and supporting surfaces. focus describes a directory's core, internal edges, external dependencies and consumers. slice gives a file's neighborhood. Hotspot ranking helps establish context; it does not by itself select the owner of your particular task.
Expected answer shape
You can name the module implementing the behavior, the contracts it consumes, its immediate consumers, and supporting tests or scripts represented in the result. Keep imports, detected runtime dispatch and keyword-only associations distinct. A shared word in a string is weaker evidence than a resolved dependency.
For example, a configuration module with many importers is a shared contract. A coordinator with few importers but many outgoing dependencies may orchestrate the behavior. Neither conclusion follows from the filename alone.
Decision
Choose the first implementation surface to inspect and list the boundaries a change must respect. If a direct test consumer appears, retain it as a verification candidate rather than automatically accepting an unrelated global test recommendation.
Check the interpretation
loct context --file src/auth/session.rs --task "session ownership and consumers" --no-aicx --markdown
loct query component-of src/auth/session.rs
Compare the task-focused neighborhood with the original map. A scope-limited result is not a whole-repository map. A large fan-in count needs its unit: importing files, edges and symbol references are different measurements.
Counterexample
A tools directory can have no import consumers and still be invoked by a Makefile, CI job or installer. An externally launched package can also have zero internal consumers. Inspect its launch/dispatch evidence before calling it decoration.
Evidence
The September round found useful directory maps across Rust, Python and JavaScript repositories, with gaps around externally launched tools. October trials found relevant direct test consumers in slice that were absent from context recommendations. These are recorded observations, not current guarantees for every repository.