{"id":"redesign-prevention-and-evolution-form-complete-maintenance-methodology","text":"The GoF provides a complete software maintenance methodology spanning both prevention and adaptation: the eight redesign causes mapped to mitigating patterns provide problem-driven preventive judgment (anticipating failures before they manifest), while patterns' role bridging software evolution phases provides curative capability (recognizing pattern-shaped opportunities during consolidation) — together these address both the anticipatory and reactive dimensions of system maintenance.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["redesign-causes-ground-preventive-pattern-judgment","patterns-bridge-software-evolution-phases"],"outlist":[],"label":"Preventive redesign mapping and curative evolution bridging are complementary halves of a complete maintenance methodology"}],"dependents":["solid-judgment-governs-complete-maintenance-methodology"],"metadata":{"source_type":"derived","review_result":"invalid"},"created_at":"2026-06-18T01:19:55+00:00","updated_at":"2026-06-18T06:15:08+00:00","reviewed_at":"2026-06-18T06:15:08+00:00","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"redesign-prevention-and-evolution-form-complete-maintenance-methodology","truth_value":"IN","reason":"SL justification valid","antecedents":["redesign-causes-ground-preventive-pattern-judgment","patterns-bridge-software-evolution-phases"],"label":"Preventive redesign mapping and curative evolution bridging are complementary halves of a complete maintenance methodology"},{"node":"redesign-causes-ground-preventive-pattern-judgment","truth_value":"IN","reason":"SL justification valid","antecedents":["eight-redesign-causes-mapped-to-patterns","pattern-selection-operationalizes-judgment"],"label":"Redesign causes provide the problem-first complement to pattern-first selection strategies"},{"node":"eight-redesign-causes-mapped-to-patterns","truth_value":"IN","reason":"premise"},{"node":"pattern-selection-operationalizes-judgment","truth_value":"IN","reason":"SL justification valid","antecedents":["six-strategies-for-pattern-selection","pattern-judgment-required"],"label":"Selection strategies are the procedural embodiment of the judgment-required principle"},{"node":"six-strategies-for-pattern-selection","truth_value":"IN","reason":"premise"},{"node":"pattern-judgment-required","truth_value":"IN","reason":"SL justification valid","antecedents":["patterns-should-not-be-applied-indiscriminately","gof-language-choice-affects-pattern-applicability","dip-overgeneralization-pitfall"],"label":"Three independent cautions converge on the need for judgment in pattern application"},{"node":"patterns-should-not-be-applied-indiscriminately","truth_value":"IN","reason":"premise"},{"node":"gof-language-choice-affects-pattern-applicability","truth_value":"IN","reason":"premise"},{"node":"dip-overgeneralization-pitfall","truth_value":"IN","reason":"premise"},{"node":"patterns-bridge-software-evolution-phases","truth_value":"IN","reason":"SL justification valid","antecedents":["gof-software-evolution-three-phases","gof-patterns-as-refactoring-targets"],"label":"Patterns function bidirectionally across Foote's three evolution phases"},{"node":"gof-software-evolution-three-phases","truth_value":"IN","reason":"premise"},{"node":"gof-patterns-as-refactoring-targets","truth_value":"IN","reason":"premise"}]}}