Detect and Track Architectural Hotspots Over Time

[akhundMurad]

Certain modules become architectural hotspots due to a combination of frequent changes, high coupling, and rule violations.

This issue proposes identifying such hotspots and tracking how they emerge, evolve, or stabilize over time.

Hotspot signals may include

• High change frequency (churn)
• High coupling (fan-in / fan-out)
• High violation density

Hotspot detection should be explainable and based on explicit thresholds or scoring.

Example insight

The payments module became an architectural hotspot starting after sprint 14.

Acceptance Criteria

• A hotspot scoring or classification mechanism is defined
• Hotspots are detectable per snapshot
• Hotspot status can be trended across snapshots
• Emerging and cooling hotspots can be identified
• Hotspot signals are explainable and documented
• Results are accessible via existing reporting outputs