improve-codebase-architecture

To identify architectural friction, analyze the codebase using the domain glossary and ADRs to find seams where complexity concentrates. This surfaces deepening opportunities that turn shallow modules into deep ones for better testability and AI-navigability.

A deepening opportunity is a refactor that turns a shallow module into a deep one by consolidating tightly-coupled code behind clearer seams. It is presented as a candidate with the involved files, the problem, the proposed solution, and expected benefits.

Use ADRs and the domain glossary to examine the codebase and identify architectural friction. By applying CONTEXT.md vocabulary, you can pinpoint shallow modules and propose refactors that improve locality, testability, and AI navigability.

This architectural analysis is applicable during both code reviews and architectural refactors across modules. It examines the codebase to surface prioritized deepening candidates that improve testability and AI-navigability in either context.

The best way to consolidate tightly-coupled modules is to analyze the codebase using the domain glossary and ADRs to generate a prioritized list of deepening opportunities. These candidates provide the files, problem, solution, and benefits for improving locality.

Your codebase lacks AI-navigability due to shallow modules and tightly-coupled code creating architectural friction. You can fix it by surfacing deepening opportunities through analyzing the domain glossary and ADRs to consolidate complexity behind clearer seams.