gxpm-architecture

To identify architectural deepening opportunities during a codebase refactor, evaluate modules for depth and seams using CONTEXT.md vocabulary and ADRs. This surfaces friction points to reduce coupling and improve testability, outputting structured candidates with impacted files and expected benefits.

Architectural deepening is the process of evaluating modules for depth and seams to reduce coupling and improve testability. It uses domain vocabulary from CONTEXT.md to maintain alignment, producing a prioritized set of refactoring candidates with problem statements and dependency handling recommendations.

Yes, you can use ADRs to guide targeted refactoring by evaluating architectural friction across modules and seams. This approach maintains domain governance and produces prioritized deepening opportunities that improve testability and AI-navigability with clear problem statements and dependencies.

Assess codebase architecture to enhance AI-navigability by reviewing CONTEXT.md and ADRs to surface architectural friction. This evaluation identifies modules lacking depth, generating a ranked list of refactoring candidates with impacted files and recommended dependency handling to improve navigability.

The best way to find architectural friction across modules and seams is to analyze the codebase using CONTEXT.md domain vocabulary and ADRs. This surfaces targeted refactoring opportunities, providing structured outputs with problem statements, dependencies, and expected benefits to reduce coupling.