improve-architecture

Architecture refactoring prioritization identifies modules with structural friction by scoring depth, leverage, and locality. It evaluates shallow wrappers and clustered helpers to determine which modules require deepening or deletion to improve maintainability.

Detecting shallow wrappers requires applying a deletion-test verdict and dependency classification to evaluate module leverage. This process identifies fragmented logic and scores whether a module provides enough depth to justify its existence or should be consolidated.

Scoring modules for testability involves assigning numeric values to depth, leverage, and locality metrics. This disciplined comparison highlights architectural friction and scattered logic, producing clear recommendations for refactoring candidates.

Architecture reviews for clustered helpers are automated by evaluating dependency classifications and applying a deletion test. This generates structured proposals that downstream refactoring workflows can consume directly without re-reading the codebase.

Modules should be consolidated or deleted when they fail the deletion-test verdict and exhibit low locality and leverage scores. This indicates severe architectural friction where the module adds complexity without sufficient depth to justify maintenance.

Module depth analysis handles scattered logic by classifying dependencies and scoring locality to find consolidation opportunities. It targets architectural friction in refactoring proposals, ensuring structured output improves testability for downstream workflows.