architecture-review

To refactor tangled code into a testable design, you diagnose architectural friction by identifying shallow, leaky, and tightly coupled modules, then propose deepening refactors through seam-focused design. This yields a settled interface and rationale without editing code.

The deletion test in architecture review evaluates refactoring candidates by measuring what happens when you inline a module's behavior into its callers. It spots pass-through modules versus those that genuinely earn their keep by evaluating deletion impact.

You find architectural friction in shallow or tightly coupled modules by analyzing seams, leverage, and locality. This frames suggestions around interfaces where behavior can be swapped and identifies where responsibility and change should concentrate.

Yes, you can use architecture review to plan refactoring without modifying code. It produces design-only architectural proposals, delivering a settled refactoring design and rationale without editing code or migrating callers.

Yes, architecture review aligns with existing project ADRs and glossary files. It consults available domain context like architecture overviews and principles to reduce vocabulary drift and avoid contradicting prior decisions.

You should use a seam-focused design for module deepening when a codebase feels tangled, hard to test, hard to navigate, or when module structure and responsibilities feel unclear. It produces concrete deepening refactoring candidates through interface analysis.