Complexity Analysis

Complexity analysis builds an observed profile from the selected version's architecture structure. Use it to find areas whose dependency density deserves explanation or redesign.

Lenses

Switch between context, module, and leaf lenses. Each lens aggregates the hierarchy differently, so its units and thresholds should be interpreted within that lens rather than compared as identical populations.

Signals

The analysis includes:

• Unique-neighbor K and interaction measures
• Dense pairs and high-pressure neighborhoods
• Structural hotspots
• Matrix and drill-down views
• An inferred observed architecture profile
• Recommendations tied to the selected evidence

A high score is not automatically a defect. Shared platform elements and deliberate orchestration can be dense for good reasons. The important question is whether the dependency pressure is intentional, owned, testable, and documented.

Unit Explorer

Use Unit explorer to search the analyzed units, filter by pressure, and change the sort order. Expand a unit to inspect its neighbors and boundary connections before interpreting its pressure index. The overview and focused evidence provide routes into Archie discussion when a signal needs explanation.

Review Workflow

1. Select the architecture lens appropriate to the question.
2. Open the strongest hotspot or dense pair.
3. Inspect its Systems and Relationships.
4. Compare it with Coupling and Blast Radius.
5. Capture an intentional pattern, risk, or decision rather than merely recording the score.