audit

Architecture complexity analysis detects technical debt by evaluating module depth, identifying leaky abstractions, and locating complexity hotspots. It applies Ousterhout's design principles to pinpoint information hiding violations for targeted refactoring.

A deep module provides a powerful interface with a simple implementation, maximizing information hiding. Module depth assessment evaluates the ratio of interface complexity to implementation complexity to identify shallow modules that increase system complexity.

Architecture debt prioritization evaluates consistency issues, layer quality, and abstraction boundaries across monoliths and services. It ranks refactoring targets by complexity impact, guiding technical debt reduction efforts toward the most critical hotspots.

Yes, Ousterhout's principles provide the framework for layer quality evaluation and abstraction boundary checks. The review process detects leaky abstractions and information hiding violations to ensure clean separation of concerns across architectural layers.

Leaky abstraction detection identifies modules where internal implementation details bleed through the interface. Analyzing codebase architecture reveals these information hiding violations by checking if module boundaries properly encapsulate complexity from callers.