Module has high inbound dependency count

How to fix

1. Review whether the module has too many responsibilities.
2. Split unrelated responsibilities into clearer modules.
3. Keep intentional shared-platform modules documented with ADR context.

What it means

Many modules depend on the same module, which may indicate a shared bottleneck.

Why it matters

High inbound dependency count increases the blast radius of changes to that module.

Common causes

• The module has become a catch-all platform.
• Shared utilities live in a feature module.
• Boundaries are too coarse.

Example bad pattern

Every feature imports a broad platform module that owns unrelated concerns.

Example good pattern

Shared dependencies are narrow, intentional, and documented.

Related files/config

• .archpilot/architecture.json
• .archpilot/contracts/*.json

Related CLI commands

• archpilot validate
• archpilot validate --ci