ALL-ARCH1007 · component_balance
Judge whether component boundaries create a maintainable size distribution.
This is a contextual rule for all languages. Read its implementation.
Definition
Section titled “Definition”Compare source volume, public surface, responsibilities, dependencies, churn, navigation, and ownership across peer packages. Size is evidence rather than an automatic violation. The criteria separately establish coherence, concentrated work, navigation cost, and a deliberate reason for asymmetric size.
Evidence
Section titled “Evidence”Findings cite component metrics, responsibilities, edges, changes, and navigation costs.
Exceptions
Section titled “Exceptions”Generated components and intentionally thin adapters may be asymmetric.
Examples
Section titled “Examples”One package owning most unrelated application behavior is oversized. Splitting every small
value type into a package can be fragmented.
References
Section titled “References”- Cites “Building Maintainable Software”, balance component size
- Cites “A Philosophy of Software Design”, deep modules
- Cites “Clean Architecture”