deepenlisted

# Deepen Find the refactors that give a module a small interface over a large body of work, ranked by evidence read in this session. The enemy is the audit by impression, with claims about files nobody opened. The overcorrection is a catalog of every improvement imaginable instead of the few that repay their migration cost. ## Scope, taken from the argument - A named target (a path, module, subsystem, layer or described pain) is matched to real paths, and the audit stays inside them. - With no target, the `exo:explorer` agent names where commit history keeps coming back, and its ranges are the scope. Widen to the whole tree only when changes scatter without a cluster or the user asks for a full audit, still through explorer ranges, because reading the tree here fills the context before any card exists. - The output opens with the scope, how it was picked and what was left out on purpose; the user is never asked to pick one. ## Terms Use these words and no substitute such as component, service, unit, API, boundary, layer or wrapper: | Term | Meaning | |---|---| | **Module** | Anything with an **interface**, what a caller must know, and an **implementation**, what it hides. | | **Deep** or **shallow** | Deep when the interface is much smaller than what it hides; shallow when learning it teaches most of the implementation. | | **Seam** | Where one implementation can stand in for another, each an **adapter**; one adapter is speculative, a second earns the seam. | | **Locali