ME.15 - Maintain Method Variants, Provenance, and Reuse

Primary working result: a maintained repertoire of admitted Method variants and separately status-preserved candidate lineages, with derivation, preserved and changed reusable semantics, applicable situations, descriptions and support editions, evidence, selection uses, currentness, and retirement conditions. For every non-variant change, the changed object, separately governed maintained result, exact affected claim or edition, and next maintenance, reconsideration, or stop action are visible.

ME.15:0 - Use This When

Use this pattern when a Method has been adapted, branched, recombined, or revised and future users must know whether they face the same Method, a reusable variant, a candidate proposal, or only a changed description, representation, tool, prompt, publication, support result, or local Work occurrence. Begin with the reusable way of doing that may have changed: which operation, dependency, role in the way of doing, entry or stop rule, or other reusable Method semantic is different?

For a first pass, write two lines: what reusable way of doing changed, if any; and, if none did, which object changed, which maintained result and exact claim or edition it affects, and what to maintain, reconsider, or stop. Continue into the fuller row only when later selection, reuse, comparison, or retirement needs it.

The first useful result is a variant-lineage row. It names the parent Method or candidate, the proposed child and status, preserved semantics, changed semantics, derivation basis, applicable situation claim, supporting and defeating evidence, descriptions and support editions, current selection uses, currentness, retirement condition, and the next decision. If the visible change is not a Method variant, the row instead names the changed object, the separately governed maintained result, the exact claim or edition affected, and the next maintenance, reconsideration, or stop action.

Here variant is Plain practice wording for a Method whose reusable semantics differ in a way relevant to a named use while its derivation from another Method remains useful. The label alone does not admit a U.Method, establish provenance, or prove fit, worth, reuse, or superiority.

Do not use this pattern merely because a file, diagram, MethodDescription edition, prompt, tool, publication form, support configuration, team, project, or dated Work occurrence changed. Maintain those results under their own patterns unless the change also alters reusable Method semantics.

ME.15:0.1 - Working Distinctions

Item	Working meaning here	Boundary
reusable Method semantics	The repeatable operations, dependencies, entry and stop rules, roles in the way of doing, transformation commitments, or other claims that distinguish how the Method is carried out and when it applies.	A wording, layout, carrier, tool, or local performance difference is not automatically semantic change.
admitted variant	An independently admitted Method whose changed and preserved reusable semantics and derivation are recoverable for the maintained use.	Derivation from an admitted parent does not admit the child.
candidate lineage	A status-preserved sequence or family of candidate accounts whose proposed semantic changes and derivations are tracked without Method admission.	A well-documented candidate does not become a MethodDescription or enacted Method.
derivation claim	The evidence-bearing claim that one Method or candidate arose through identified changes from another.	Similarity of names, files, or outcomes does not establish derivation.
preserved semantics	Reusable Method claims intentionally retained across the derivation.	“Mostly the same” is insufficient when the receiving use depends on the omitted difference.
changed semantics	Reusable Method claims added, removed, reordered, constrained, generalized, specialized, or recomposed in the proposed child.	A local departure in one Work occurrence remains a deviation until reusable semantics are recovered.
applicability entry	A bounded claim about situations, capability and support conditions, evidence, and stops for selecting or rejecting a variant.	It is not practical worth, organization-wide adoption, or a selection command.
edition and support link	The MethodDescription, representation, method-base edition, publication, tool, prompt, or support result currently used for a variant.	These results can change without changing variant identity and can serve several variants only when their claims permit it.
retirement condition	A named evidence, currentness, source, use, or replacement condition under which an entry stops being offered for the maintained selection use.	Retirement from one repertoire use does not erase the Method, its history, or every other use.

ME.15:1 - Problem Frame

Method adaptation leaves many visible traces: a team edits a checklist, adds a tool, changes a diagram, rewrites a prompt, or performs the Work differently. Some traces express a reusable change in the way of doing; others are only descriptions, support configurations, local departures, or evidence. Treating every trace as a Method variant floods the repertoire with false identities. Treating none as a variant hides meaningful branches and makes later fit and worth evidence impossible to bind to the semantic branch they concern.

The practical question is whether reusable Method semantics differ for the named use, what derivation is supported, and which status, applicability, evidence, and currentness claims can be maintained while keeping candidate accounts distinct from admitted Methods.

ME.15:2 - Problem

Version numbers, filenames, team names, tool stacks, and project histories become variant identifiers. A successful local adaptation is generalized without an admitted reusable Method. Candidate recombinations inherit parent admission. A new MethodDescription edition is mistaken for a new Method, while a real change to operation order or stop conditions is hidden as documentation maintenance.

The resulting repertoire cannot guide selection. Users cannot tell which semantics changed, whether evidence applies to parent or child, what support edition is current, which situation claim is supported, or when an entry should be retired.

ME.15:3 - Forces

Force	Tension
Reuse	Stable variant identities help later selection, while premature naming creates spurious Methods.
Local adaptation	Work must respond to situations, while one local departure need not be reusable semantics.
Provenance	Derivation helps explain and compare variants, while similarity and chronology can be mistaken for evidence.
Evidence	Fit and worth results should follow the right semantics, while evidence often bundles Method, support, capability, and organization.
Currentness	Users need current entries and editions, while retirement from one use must not erase history.
Candidate continuity	Proposed changes need traceability, while detailed lineage can launder candidate status.
Recombination	Components can inspire new Methods, while untested hybrids do not inherit component admission or worth.

ME.15:4 - Solution

Identify variants only through changed reusable Method semantics, preserve admission or candidate status independently, and maintain derivation, applicability, evidence, editions, selection uses, currentness, and retirement as separate claims.

ME.15:4.1 - Pattern-Use Unfolding

Name the maintenance use. Identify the practitioner or decision that needs the repertoire, the Method family or candidate lineage in scope, the situation and qualification window, and what selection, reuse, comparison, or retirement action the entry must support.
Recover each subject and status. Identify every A.3.1-admitted Method and every candidate account separately. A parent Method, candidate child, MethodDescription, representation, support configuration, and Work occurrence keep different identities and statuses.
Recover the semantic baseline. From the parent or earlier candidate, record the reusable operations, dependencies, entry and stop rules, roles in the way of doing, required relations, and applicability claims that matter to the maintenance use. Do not use a file diff as the semantic baseline.
Classify the observed change. Separate changed reusable Method semantics from description wording, representation, publication, tool, prompt, support, capability, organizational System or selected structure, assignment, permission, authority, and local Work deviations. For every non-semantic change, name the changed object, the separately governed maintained result, the exact claim or edition affected, and the next maintenance, reconsideration, or stop action. For a representation change, locate the affected claim in the one-action C.37 result or, when several unlike Method-related actions are related, in the ME.9 profile. Use step 8 for the complete maintained profile basis. Name a direct predicate and its participants only when the disposition relies on that obtaining relation; otherwise assert no path or relation occurrence.
Construct the proposed child account. State preserved semantics, changed semantics, reason for change, intended situations, required capability and support conditions, and the limits of the available evidence. A traceable candidate entry can complete the maintenance use. Select further evidence or a trial through C.11.DUA only when its obtainable result could change the receiving decision enough to warrant the full burden. If no reusable semantic difference remains, maintain an edition, support, or Work result rather than a variant.
Establish derivation without inheriting admission. Record the source Method or candidate, change Work or source account, changed positions, chronology when relevant, and evidence supporting the derivation claim. Then admit the proposed child independently under A.3.1 or keep it as a candidate.
Bind evidence to the right semantics and situation. Attach available ME.11 trial observations, ME.12 corrections, ME.13 fit or transfer results, and ME.14 worth decisions only to the Method or candidate semantics, situation, support, capability, alternative set, and window they actually concern. Parent evidence does not automatically cover the child.
Maintain descriptions, Method representation profiles, and support relations separately. Name current ME.8 MethodDescription editions, complete ME.9 profiles, ME.10 method-base and support results, publications, tools, prompts, and any exact access or use relation that serves the variant use. For every ME.9 profile retain the shared MethodDescription or candidate-account source, one complete C.37 claim group for each unlike action, cross-use correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions for reconsidering several selections. A changed result, edition, or relation does not by itself change variant identity.
State applicability and selection uses. Record supported situations, defeated situations, missing evidence, capability and support conditions, current alternative set, and the receiving decision that may use the entry. Use A.19 selected-set semantics for a non-trivial repertoire choice; the entry itself selects nothing.
Maintain currentness and retirement. State source, evidence, edition, situation, and qualification windows; superseding or defeating evidence; review trigger; and what retirement means for this use. Preserve historical and other-use access when the Method or candidate still matters elsewhere.
Return the maintained repertoire and non-variant dispositions. Report admitted variants, candidate lineages, applicability and evidence gaps, current entries, retired entries, and the smallest repertoire claim reopened by defeated applicability, evidence, currentness, or retirement evidence. For every non-variant, report the changed object, separately governed maintained result, exact affected claim or edition, and next maintenance, reconsideration, or stop action. Do not assign repair authority or invent a relation when the governing result and next action are sufficient.

ME.15:4.2 - Record the Result

Result position	Required content
maintenance use	Practitioner or receiver, repertoire decision, situation, qualification window, and stop.
subject and status	Parent and child Methods or candidate accounts; separate descriptions, representations, support results, Work, and evidence.
semantic baseline	Reusable operations, dependencies, entry and stop rules, roles in the way of doing, relations, and applicability claims relevant to the use.
change classification	Changed reusable semantics; for each non-variant, the changed object, separately governed maintained result, exact affected claim or edition, and next maintenance, reconsideration, or stop action.
derivation	Parent, proposed child, change basis, chronology when material, preserved semantics, changed semantics, and evidence reach.
admission branch	Independent Method admission or status-preserved candidate account and missing admission basis.
applicability and evidence	Situations, capability and support conditions, the available evidence and decisions from step 7, alternatives, gaps and qualification windows, all bound to the right semantics and receiving use.
edition and support links	Current descriptions; current ME.9 profiles with the complete basis named in step 8; method-base editions, publications, tools, prompts, and support results for each maintained use.
currentness and retirement	Current selection uses, source and evidence windows, defeating conditions, retirement meaning, retained history, and reopen trigger.
return	Maintained admitted-variant repertoire and candidate lineages; non-variant dispositions in the same four-part shape; the smallest defeated repertoire claim when one exists; and limits on what the repertoire establishes.

ME.15:4.3 - What Changes in Practice

Teams stop using version labels and project names as Method identities. They can show which reusable semantics changed, which evidence belongs to which branch, why a child is admitted or still a candidate, and which description or support edition serves each use.

The repertoire becomes smaller and more useful. Local departures can remain Work evidence, descriptions can evolve without multiplying Methods, and real semantic branches receive applicability, evidence, currentness, and retirement conditions.

ME.15:4.4 - Minimal Constructed Variant Replay

Continue the temperature-sensor review chain. M-Unit-Review-1 is admitted with reusable semantics: identify every source unit, normalize values, compare with declared tolerance, and stop on an unresolved mismatch. ME.14 retained it for reports whose sources can use different unit systems.

A team proposes an approximation rule for missing conversion metadata: infer a likely scale from sensor range, mark the inference, and continue only when the tolerance decision is unchanged under both plausible scales. This is not merely a new checklist. It changes the reusable operation and stop conditions, so create candidate account C-M-Unit-Review-Approx-1 derived from M-Unit-Review-1. Preserve identification, explicit normalization when metadata exists, tolerance comparison, and unresolved-mismatch stop; add the bounded inference operation and a two-scale invariance stop.

Do not admit the candidate from parent status. Link candidate-account content CA-M-Unit-Review-Approx-Content-1, proposed representation C-REP-Approx-1 of that candidate account, and the same conversion-table support result only as candidate-serving material; none is a U.MethodDescription for the candidate whole. Keep performance on missing-metadata reports unresolved. Retain that limit, the reviewer capability conditions and the comparison against stopping or metadata recovery where they matter to the entry’s use. To maintain the catalogue, record the proposed approximation rule, its origin in M-Unit-Review-1, its two-scale stopping condition and its untested candidate status. This is enough to retain the proposal in the catalogue. Choose a trial only when its useful attainable answer warrants the work and delay. Until independent admission and evidence exist, the repertoire contains admitted M-Unit-Review-1 plus candidate lineage C-M-Unit-Review-Approx-1; no Work is said to enact the candidate whole.

If the team only updates the diagram to show the already-required normalization step, first identify its exact action. For one action, maintain the complete C.37 representation-use result and the diagram under its direct governor; ME.9 is not invoked. When that result belongs to a complete ME.9 profile for several unlike actions, also maintain only the cross-use correspondences, conflicting omissions, edition relations, decisions to keep representations separate, and conditions for reconsidering several selections affected by the diagram change. Neither case creates a variant. If the team replaces the manual table with a verified tool while operations and stops remain unchanged, maintain the ME.10 support result and no variant.

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.

ME.15:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
file-version bias	Every document or repository version becomes a Method variant.	Compare reusable Method semantics; for an edition-only change, name the maintained result, exact edition claim, and next maintenance or stop action.
local-deviation bias	One Work departure becomes a reusable Method.	Recover repetition, intended reuse, semantic account, and independent admission; otherwise keep Work evidence.
inherited-admission bias	A child or hybrid inherits parent Method status.	Admit every proposed Method independently or preserve candidate status.
tool-identity bias	A new prompt, tool, or platform becomes the variant.	Ask which reusable operations or stops changed; maintain support when none did.
evidence-smearing bias	Parent fit or worth evidence is attached to every descendant.	Bind evidence to semantics, situation, support, capability, alternative set, and window.
lineage-as-worth bias	Detailed provenance is treated as evidence that the branch should be selected.	Keep derivation, applicability, and practical worth as separate claims.
retirement-erasure bias	Retirement from one repertoire use deletes history and other uses.	State the retired selection use and preserve the Method, lineage, and evidence where still needed.

ME.15:7 - Conformance Checklist

One maintenance and selection use, receiver, situation, window, and stop are named.
Every parent and child is independently admitted as a Method or preserved as a candidate account.
Reusable Method semantics are recovered before variant identity is claimed.
Preserved and changed semantics are explicit and decision-relevant.
Description, representation, publication, tool, prompt, support, capability, organization, and local Work changes remain separately governed.
Derivation has an evidence basis and does not transfer admission.
Trial, coherence, fit or transfer, and worth evidence is bound to the right semantics, situation, conditions, alternatives, and window.
Current description and support editions are linked without defining variant identity.
Applicability, missing evidence, selection use, currentness, and retirement conditions are recoverable.
Recombination candidates inherit neither parent admission nor parent worth.
A useful candidate entry can complete its maintenance use with the relevant evidence limits. Any further trial is selected for its useful obtainable contribution and full burden.

ME.15:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
“Version 2.1 is a new Method variant.”	Show the changed reusable Method semantics or maintain an edition only.
“The team adapted it, so the variant is admitted.”	Preserve the Work evidence and candidate account until independent admission.
“The AI prompt defines the new Method.”	Recover the way of doing and support relation; a prompt can serve but not identify the Method by itself.
“The hybrid inherits evidence from all three parent Methods.”	Preserve candidate status and bind each relied-on result to the hybrid’s own semantics and situation. Select a trial when its useful attainable answer warrants its full burden.
“Retired means obsolete everywhere.”	Name the selection use and defeating condition; preserve other supported uses and history.

ME.15:9 - Consequences

Variant repertoires show the reusable semantic differences and the evidence for each branch. Practitioners can select among stable admitted Methods and visible candidate branches without confusing package change with Method change.

The cost is more disciplined status and provenance work. Some attractive adaptations remain candidate lineages, and teams must keep descriptions, support editions, evidence, and selection uses linked without letting any one of them define identity.

ME.15:10 - Rationale

Reuse depends on knowing what way of doing is being reused. Files and tools can carry or support that way, and Work can reveal changes, but only reusable semantic change distinguishes a Method variant for the maintained use. Derivation does not supply the child’s Method admission; that admission is checked independently.

Maintaining applicability, evidence, currentness, and retirement with the variant prevents a static family tree. The result is a repertoire for decisions rather than a genealogy or archive alone.

ME.15:11 - SoTA-Echoing

Source	Adopted or adapted contribution	Boundary and practitioner implication
Schønheyder and Nordby, design-Method use and evolution in professional practice	Adopt cyclic evolution, project demands, practitioner skill sets, organization, and observed adaptation as inputs to variant and applicability maintenance.	One multidisciplinary design firm supplies neither a universal variant taxonomy nor independent admission or causal effect.
Faludi, Yiu, and Agogino, empirical tests of sustainable-design Methods	Adopt activity- and mindset-level observations across three Methods and industries as evidence that can motivate bounded branch or recombination questions.	Immediate self-report does not establish long-term results, hybrid-Method admission, or the worth of recombined variants.
Gericke et al., method ecosystems, and Stacey et al., Methods as engineering knowledge	Adopt maintained Method ecology, content, representation, use, and change questions for the repertoire account.	Position and knowledge contributions do not show that one repository, support stack, or variant organization works universally.
Current FPF `A.3.1`, `A.3.1.MR`, `C.2.1`, `A.10`, `G.5`, `G.11`, and A.19 selected-set semantics	Reuse Method admission, candidate recovery, edition identity, evidence use, registered Method-family candidate sets, and non-forced selection. ME.15 itself records local source, evidence, situation, qualification-window, defeating-evidence, and retirement claims. Invoke G.11 only when the entry participates in a G.11-admitted shipped pack, evidence or selected set, archive or front, publication/currentness object, dependency on a reused A.6.RCD predicate definition or derived relation kind, or another condition named by G.11.	ME.15 contributes Method-variant semantic classification, derivation, applicability, and local maintenance. It neither redefines those governors nor turns every repertoire-entry currentness or retirement question into refresh orchestration.

Reopen the pattern when practitioners cannot distinguish reusable semantic change from local Work or support change, when a mature source supplies a stronger variant identity and retirement method, when a new case demonstrates an independently useful lineage problem not covered here, or when current FPF Method and repertoire semantics change the result.

ME.15:12 - Relations

ME.11 supplies actual adaptation and deviation evidence; ME.12 supplies corrections tied to exact contradicted claims and maintained results; ME.13 supplies applicability, fit, failure, and transfer limits; ME.14 supplies bounded practical-worth and branch decisions. None identifies a variant without changed reusable Method semantics.
ME.8 maintains descriptions; C.37 maintains one-action representation-use results; ME.9 maintains complete Method representation profiles for several unlike Method-related actions, including their action rows and separate cross-use result; ME.10 maintains method-base editions, publications, tools, prompts, and support results. A lower representation remains with its direct FPF governor. Changes to any of these results do not automatically change Method identity, and a non-variant disposition names the changed object, maintained result, exact affected claim or edition, and next action.
A.3.1 governs Method admission. A.3.1.MR can recover a candidate Method from Work evidence under its conditions. C.2.1 governs episteme and edition identity; A.10 evidence use; G.5 registered Method-family candidate sets; A.19 comparison and selected-set semantics.
ME.15 records local source, evidence, situation, qualification-window, defeating-evidence, currentness, and retirement claims. Open G.11 refresh orchestration only for one of its named shipped packs, evidence or selected sets, archives or fronts, publication/currentness objects, dependencies on reused A.6.RCD predicate definitions or derived relation kinds, or another G.11-admitted condition.
A.3.4 governs any separate claim that one continuing carrier, organizational System, selected structure, or other subject actually changed across a bounded occurrence. A semantic difference, derivation account, edition relation, or local Work deviation does not by itself establish a U.Transformation.
ME.16 consumes a maintained admitted variant or status-preserved candidate entry when attempting a bounded introduction. ME.17 uses either an independently admitted Method Engineering Method with actual enactment or a status-preserved candidate or observed-practice branch without Method or enactment inflation; neither inherits admission or worth from the repertoire.