improve-codebase-architecture

Improving codebase architecture involves analyzing repository docs, caller paths, and validation evidence to distinguish shallow pass-throughs from valuable seams. This process identifies testable boundaries and classifies dependency shapes to ensure adapters match reality.

The deletion test is a confidence rubric applied during architecture review to verify module value. It guides interface design by ensuring tests and callers cross the same seam, preventing premature interface proposals and focusing on high-leverage deepening.

Generating an architecture review report requires producing a verifiable HTML document with before and after diagrams. This report uses the repository's domain vocabulary and durable ADR constraints to visualize evidence-backed deepening opportunities.

Yes, this architecture review approach supports ports and adapters refactoring by classifying deepening strategies as in-process, local-substitutable, ports and adapters, or mock. This classification ensures your dependency shape matches reality during interface design.

Evidence-based architecture deepening is not appropriate when you need to propose interfaces prematurely or lack sufficient validation evidence. This approach requires analyzing existing repository docs and caller paths, making it unsuitable for greenfield projects without modular codebases.