{"id":"formalization-grounds-expert-methodology","text":"The GoF's complete pattern lifecycle methodology (preventive redesign mapping, curative refactoring targets, systematic seven-step application process) is grounded by the formalization heritage's empirical validation requirement (Known Uses across at least two domains), ensuring the methodology operates on empirically confirmed patterns rather than speculative abstractions.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["patterns-complete-lifecycle-methodology","known-uses-validates-empirical-formalization"],"outlist":[],"label":"Empirical validation grounds the methodology; methodology operationalizes the validated knowledge"}],"dependents":["design-knowledge-empirically-grounded-methodology"],"metadata":{"source_type":"derived","review_result":"pass"},"created_at":"2026-06-17T23:32:57+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":"formalization-grounds-expert-methodology","truth_value":"IN","reason":"SL justification valid","antecedents":["patterns-complete-lifecycle-methodology","known-uses-validates-empirical-formalization"],"label":"Empirical validation grounds the methodology; methodology operationalizes the validated knowledge"},{"node":"patterns-complete-lifecycle-methodology","truth_value":"IN","reason":"SL justification valid","antecedents":["patterns-preventive-and-curative","gof-systematic-pattern-application-method"],"label":"Preventive-curative dual roles combined with systematic selection and application process yields a complete pattern lifecycle methodology"},{"node":"patterns-preventive-and-curative","truth_value":"IN","reason":"SL justification valid","antecedents":["eight-redesign-causes-mapped-to-patterns","gof-patterns-as-refactoring-targets","gof-software-evolution-three-phases"],"label":"Patterns address redesign causes before they manifest AND guide refactoring after code evolves"},{"node":"eight-redesign-causes-mapped-to-patterns","truth_value":"IN","reason":"premise"},{"node":"gof-patterns-as-refactoring-targets","truth_value":"IN","reason":"premise"},{"node":"gof-software-evolution-three-phases","truth_value":"IN","reason":"premise"},{"node":"gof-systematic-pattern-application-method","truth_value":"IN","reason":"SL justification valid","antecedents":["six-strategies-for-pattern-selection","seven-steps-to-apply-a-pattern"],"label":"Two complementary methodological elements (selection + application) form a complete procedural framework"},{"node":"six-strategies-for-pattern-selection","truth_value":"IN","reason":"premise"},{"node":"seven-steps-to-apply-a-pattern","truth_value":"IN","reason":"premise"},{"node":"known-uses-validates-empirical-formalization","truth_value":"IN","reason":"SL justification valid","antecedents":["pattern-formalization-heritage","gof-known-uses-two-domains-minimum"],"label":"Two-domain evidence requirement operationalizes Alexander's empirical principle"},{"node":"pattern-formalization-heritage","truth_value":"IN","reason":"SL justification valid","antecedents":["design-patterns-originated-from-christopher-alexander","gof-pattern-four-essential-elements","gof-design-pattern-template-sections"],"label":"Each formalization step increased precision — from analogy, to essential structure, to systematic documentation template"},{"node":"design-patterns-originated-from-christopher-alexander","truth_value":"IN","reason":"premise"},{"node":"gof-pattern-four-essential-elements","truth_value":"IN","reason":"premise"},{"node":"gof-design-pattern-template-sections","truth_value":"IN","reason":"premise"},{"node":"gof-known-uses-two-domains-minimum","truth_value":"IN","reason":"premise"}]}}