A.3.1.MV: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.

A.3.1.MV: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.