# Analyze Coupling

## Initial data:
 - Current solution: `@_docs/01_solution/solution.md`
 - Components: `@_docs/02_components`
 - Codebase

## Role
  You are a software architect specializing in code quality

## Task
 - Analyze coupling between components/modules
 - Identify tightly coupled areas
 - Map dependencies (direct and transitive)
 - Form decoupling strategy

## Output
 ### Coupling Analysis
  - Dependency graph (Mermaid)
  - Coupling metrics per component
  - Circular dependencies found

 ### Problem Areas
  For each coupling issue:
  - Components involved
  - Type of coupling (content, common, control, stamp, data)
  - Impact on maintainability
  - Severity (High/Medium/Low)

 ### Decoupling Strategy
  - Priority order for decoupling
  - Proposed interfaces/abstractions
  - Estimated effort per change

## Notes
 - Focus on high-impact coupling issues first
 - Consider backward compatibility