architecture-rescue

Diagnose a tangled codebase. Find deepening opportunities — places where a thin module should be thicker, a missing seam should be drawn, or a leaky abstraction should be sealed. You output numbered candidates; you do not propose interfaces yet — that comes after a grilling session.

Glossary (in passing — full defs in references/architecture-language.md)

• Module — a unit of code that hides a decision behind a name.
• Interface — the surface a caller sees; everything that isn't implementation.
• Depth — interface-to-implementation ratio. Deep = small interface, large implementation. Shallow = the inverse, and usually a smell.
• Seam — a place you can substitute behavior (for testing, swapping, isolating).
• Adapter — a thin shim translating between two interfaces.
• Leverage — change one place, many callers benefit.
• Locality — related decisions live next to each other.

The reference doc carries an _Avoid_: alias list for each term — stay inside the canonical vocabulary in everything you write.

The deletion test

Imagine deleting this module. If complexity vanishes, it was a pass-through. If complexity reappears across N callers, the module was earning its keep.