ME.15:5 - Archetypal Grounding - Adaptation and Recombination

The Halogen design-practice case reports conscious cyclic evolution and adaptation of Methods across safety-critical projects, practitioner skill sets, and organization of design activity. Use the evidence to recover proposed semantic changes, local Work deviations, situation conditions, and lineage candidates. The source concerns one 52-person multidisciplinary firm and does not supply a universal variant family or automatic Method admission.

When reusable semantics can be recovered and a Method is independently admitted, maintain the variant with its derivation and applicability. When interviews, observations, or documents show only local departures or cannot distinguish changed Method semantics from changed support, capability, or organization, maintain a candidate lineage or return the missing semantic basis.

The sustainable-design study reports activity- and mindset-level observations from separate workshops using The Natural Step, Whole System Mapping, or Biomimicry. Companies chose workshops, order varied, and participants could differ, so the publication supplies neither one current-alternative decision nor matched Work across the three Method families. Those immediate participant reports can motivate recombination candidates, but a preferred component set is not an admitted hybrid Method. Record the proposed preserved and changed semantics, parent contributions, situations and evidence limits; do not inherit worth or transfer from the source Methods.

ME.15:5.1 - APP-ME-01 Candidate Lineage

Maintain editions of C-EC-Release-v2 as a candidate lineage until A.3.1 admits a Method with recoverable reusable semantics. Keep the four admitted constituent Methods, their descriptions, representations, PLM and CI Systems, prompts, support arrangements, release Work, and local deviations separate.

A changed release document, cadence, tool integration, AI prompt, or method-base edition does not create a C-EC-Release-v2 variant by itself. A proposed semantic change must name the changed reusable operation, dependency, entry or stop rule, or another Method claim and preserve the candidate branch. Unsupported CUR-EC417-CadenceEffect-1 remains unsupported.