improve-codebase-architecture

To find shallow modules and leaky seams, an architecture exploration pass walks the codebase to spot boundaries where tests can't effectively exercise behaviour, then proposes deepening opportunities that concentrate logic behind small interfaces.

Refactoring for testability and interface leverage involves identifying shallow boundaries and proposing deepening candidates that concentrate behaviour behind small interfaces, framed using vocabulary like depth, seam, adapter, locality, and leverage.

An architecture deepening report helps consolidate tightly coupled modules by generating a self-contained HTML review with before/after diagrams and evidence, showing how to increase interface leverage and maintain locality.

Yes, an exploration pass over domain vocabulary and relevant ADRs is required before proposing refactoring candidates, ensuring deepening opportunities align with existing design decisions and improve AI-navigability.

Constraints and seam placement are defined through an interactive refactoring grilling loop that runs a constraint-driven design conversation to crystallize the deep module shape, dependencies, and testing approach.

A deepening approach for architecture improvement may not suit contexts where module boundaries already exhibit high interface leverage and strong locality, as the process targets shallow modules and leaky seams that hinder testability.