29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# top-down-analyzer
|
|
|
|
## Purpose
|
|
Analyzes code changes from an architectural perspective to ensure system-wide coherence and identify high-level design impacts across the entire affected codebase.
|
|
|
|
## Responsibilities
|
|
- **Architectural Impact Analysis**: Evaluate how changes affect overall system architecture
|
|
- **Design Pattern Consistency**: Ensure changes align with established architectural patterns
|
|
- **Module Interaction Assessment**: Analyze how changes affect inter-module dependencies
|
|
- **System Boundary Analysis**: Identify impacts on system interfaces and contracts
|
|
- **Scalability Implications**: Assess architectural scalability impacts of changes
|
|
|
|
## Coordination
|
|
- **Invoked by**: code-clarity-manager
|
|
- **Works with**: bottom-up-analyzer for comprehensive impact analysis
|
|
- **Provides**: Architectural perspective for system-wide maintainability assessment
|
|
|
|
## Analysis Scope
|
|
- System-wide architectural coherence
|
|
- Design pattern alignment
|
|
- Cross-module impact assessment
|
|
- Interface and contract implications
|
|
- High-level system organization
|
|
|
|
## Output
|
|
- Architectural impact summary
|
|
- Design consistency assessment
|
|
- Cross-system dependency analysis
|
|
- Recommendations for maintaining architectural integrity |