architecture-lens

Assess architectural integrity by evaluating module boundaries, interface clarity, and separation of concerns to identify structural faults and evolution blockers. This review reveals whether your system design can sustain future changes without hidden failures.

Analyze coupling and cohesion by tracing dependency directions, flagging circular dependencies, and identifying inappropriate reliance on concretions. This structural review ensures clear module boundaries and prevents dependencies that block system evolution.

Review resilience by examining retry and backoff strategies, timeouts, graceful degradation, and idempotency to identify single points of failure. This fault-tolerance review highlights runtime failure scenarios and recommends mitigations for robust system design.

Yes, you can evaluate evolutionary fitness during change proposals by determining how easily your design adapts to likely future requirements. The assessment evaluates whether tradeoffs are acknowledged and produces actionable findings with confidence ratings.

You need an architecture review during pull request evaluations and post-incident assessments when module boundaries, dependencies, and failure modes must be understood. It provides structured findings to ensure changes do not introduce structural faults or evolution blockers.