Status: IN
Design patterns bridge software evolution phases: they capture the structures that emerge during consolidation (refactoring to generalize) and, when applied preemptively during expansion, prevent the accumulation of design debt that triggers future consolidation cycles — making patterns both diagnostic and preventive tools for managing software evolution.
Patterns function bidirectionally across Foote's three evolution phases
Depends on (SL): gof-software-evolution-three-phases, gof-patterns-as-refactoring-targets