Architectural fragmentation is the loss of system-wide coherence when local decisions produce duplicated approaches, inconsistent integration styles, unclear cross-cutting ownership, and accumulating technical debt. It emerges when autonomy is mistaken for global architectural responsibility. section 1.2
Fragmentation commonly appears when:
- Short-term optimizations override long-term system health. section 1.2
- Non-functional requirements are postponed or ignored. section 1.2
- Teams make local decisions without seeing system-wide effects. section 1.2
- No one owns coherence across the whole system. section 1.2
The remedy is neither automatic centralization nor unconstrained autonomy. Make responsibility for architectural consequences explicit, then carry it through delivery, feedback, and change. section 1.2
Figure 1.2 Architectural responsibility can be centralized, distributed, or left unclear. The real risk is not the absence of an architect title, but the absence of clear ownership for cross-cutting technical decisions.

Use the figure to compare centralized, distributed, and unclear responsibility, focusing on ownership of cross-cutting technical decisions. section 1.2
