Part I - Method Focus, Architecture History, Repertoire, Situational Criteria, and Recovery

ME.1 - Choose and Reopen the Project’s Method-Engineering Focus

Primary working result: a Method-focus result that selects one Method, an established family or explicitly local grouping, a set of Method relations, or a non-Method return for one project decision. The result preserves every Method or candidate-account status and names one observation that would reopen the focus.

ME.1:0 - Use This When

Use this pattern when a project says that its “methodology”, “process”, “workflow”, or “way of working” must change, but the decision subject is still ambiguous. The live concern may be one Method, several related Methods, an established Method family, a temporary comparison grouping, or something else such as a tool, capability, support arrangement, description, resource, or project System.

Begin with the result that is missing, late, unsafe, or too costly and the representative Work in which that result matters. Recover the Methods and candidate accounts already visible there before choosing the level of focus.

The first useful move is to compare four possible focus classes: one Method; an established family or project-local grouping; named Method relations; and a non-Method return. The practical gain is that later repertoire, qualification, or architecture Work receives the smallest subject it can act on without inventing a Method or a composite.

Do not use ME.1 merely because one tool failed, one practitioner lacks capability, one document is incomplete, or one project, process, or case view is inconvenient. Return that question to its direct subject unless changing a Method would change the receiving result.

ME.1:0.1 - Working Distinctions

ME.1:1 - Problem Frame

Project teams encounter Methods through handbooks, standards, stage models, issue trackers, training, job titles, toolchains, and remembered practice. These can reveal useful Methods, but their visible boundaries rarely coincide with Method identity.

A project schedule can describe intended Work, a process account a reusable Method, and a case account the condition or acceptance of a named result. These descriptions can reveal connected Method questions without sharing a subject. When several accounts actually concern one admitted Work, preserve that identity across them. Recover the claim and subject before selecting a viewpoint; changing a representation creates neither another Work nor a Method.

ME.1:2 - Problem

A focus chosen too broadly turns every artifact and supporting System into a Method part. A focus chosen too narrowly optimizes one operation while the receiving result still depends on several Methods or a support relation. A familiar label can also turn a project-local shortlist into an alleged professional family.

The project then asks the wrong downstream question. It builds a repertoire for a tool problem, qualifies a candidate account as though it were an identified Method, or compares “architectures” that are only differently drawn views of the same Work.

ME.1:3 - Forces

ME.1:4 - Solution

Select the smallest focus class whose subject and status are supported and whose change could alter the receiving result. Keep the rejected focus options and one observable reopen condition in the result.

ME.1:4.1 - Pattern-Use Unfolding

1. Name the receiving result and decision. State the result at risk, who will use it, the relevant situation and interval, and what decision the focus will enable.
2. Recover representative Work. Identify the Work occurrence or intended Work that exposes the difficulty. Use A.15.6 to keep the project System, use, Work, Method, support, and development subjects distinct.
3. Recover the subjects of the accounts already in use. For each project, process, case, lifecycle, stage, or workflow description, state what its claims concern, their actual or intended status, the question exposed, and the material omissions. Use A.15.6 when the label hides the subject. Keep unlike subjects separate; a claimed view additionally needs its exact viewpoint and E.17.0 conformance result.
4. Recover Method-status candidates. List Methods already identified under A.3.1, candidate Method accounts, established family facts, local groupings, related Methods, and support or capability alternatives. Preserve their statuses.
5. Form materially different focus options. Include each plausible one-Method, plurality, relation, and non-Method branch. A renamed package or differently drawn view is not another focus option.
6. Test family and relation claims. Use G.5 for any maintained family or selector claim and the applicable relation pattern for each direct relation. When no identified whole and obtaining relations exist, retain a relation focus or local grouping rather than a composite.
7. Choose and record. Use C.11 or a domain decision Method to select one focus for the receiving decision. State rejected options, evidence limits, next useful result, and the observation that reopens the focus.

ME.1:4.2 - Record the Result

ME.1:4.3 - What Changes in Practice

The project stops asking which named methodology should replace another. It first decides whether the live subject is one Method, a governed family or local grouping, relations among several Methods, or a non-Method condition. Downstream Work becomes smaller, and a useful plurality can remain plural without being packaged as a fictitious composite.

ME.1:5 - Archetypal Grounding — EC-417 Release Focus

In the EC-417 release scenario, eight of twenty releases reopened. The package is commonly called the “release methodology”, so the first proposal is to replace it as one Method.

Three management questions expose different subjects in this scenario:

The status inventory contains four identified Methods: M-HW-Verify, M-SW-Integrate, M-Supplier-Approve, and M-Release-Authorize. It also contains candidate accounts C-Evidence-Reconcile-Internal, C-Evidence-Reconcile-Supplier, and C-AI-Trace-Review. C-EC-Release-v2 is only a proposed-whole account. The PLM, CI, test rig, AI provider, safety capability, and supplier responsibility are support, System, capability, access, or assignment subjects rather than Method candidates by position.

The schedule exposes a timing conflict, the reusable accounts expose the checks and guards, and the case question identifies the evidence condition still to settle. These connections support a Method-relation focus without making the three subjects one Work. The first result is therefore a Method-relation focus. It creates no fifth Method and no composite. Reopen to a test-capability focus if two of the next three comparable delays occur while required evidence is complete and the rig is unavailable.

ME.1:6 - Bias-Annotation

ME.1:7 - Conformance Checklist

• The Method-focus result names the receiving result, representative Work, and current decision.
• Every Method and candidate account keeps its prior status.
• An established family cites an independent classification or membership basis.
• A project-local grouping states its criterion, use, and non-family status.
• Project, process, and case accounts preserve their actual direct subjects and intended or performed status; a claimed view has its own viewpoint-conformance basis.
• The options include a non-Method return whenever a tool, capability, support arrangement, description, resource, or System could be decisive.
• The selected focus states rejected focus options, uncertainty, next useful result, and an observable reopen condition.
• Method, family, relation and composite claims rely on their identifying evidence; package position, a view or shared use alone is not that evidence.

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

ME.1:9 - Consequences

Method Engineering begins with a decision-usable subject instead of a fashionable label. Later repertoire and criteria Work can remain narrow, while a relation focus exposes genuine coordination questions without pre-committing to a whole.

The cost is a short recovery of Work, views, statuses, and non-Method alternatives. Some projects will stop before Method Engineering because the useful answer concerns a support System, capability, description, or resource.

ME.1:10 - Rationale

The focus determines which claims are admissible in later Method use. Preserving the difference among a Method, family, local grouping, relation focus, and non-Method subject prevents downstream qualification or architecture prose from silently upgrading an unsupported object.

ME.1 connects questions about Methods, their descriptions, Work, capability, tools, variants and Method change. Project, process and case accounts help discover those questions. Recovering each claim’s subject before selecting its representation preserves both useful accounts of one Work and useful connections among different subjects.

ME.1:11 - SoTA-Echoing

Reopen the affected rule when a current source or representative use exposes another materially different focus class, or when an account’s subject, status, or omitted claim changes the Method question or non-Method return.

ME.1:12 - Relations

• A.15.6 distinguishes project subjects and routes a Method-of-interest question here.
• A.3.1 governs Method identity; G.5 governs maintained family and selector results; C.11 governs the bounded focus choice.
• ME.2 may organize a repertoire for a one-Method, plurality, or relation focus. ME.3 may state criteria at that same level of focus.
• ME.5 receives identified Methods and candidate accounts without changing their status. ME.6 receives a several-structure question; ME.7 receives one proposed whole only when that question is live.
• ME.19 may explain an identified Method, established family inclusion, or named relations. A local grouping label is not its explanandum.

ME.1:End

ME.19 - Recover Why and How a Professional Method Architecture Differentiated

Primary working result: a differentiation account with a dated sequence, named pressure/response/variation/selection links, serious rivals, diagnostic observations, and graded claims. When a receiving decision needs causal reliance, ME.19 also returns one separate C.28 causal-use support result; the downstream architecture decision remains a third episteme.

ME.19:0 - Use This When

Use this pattern when an identified Method, independently established family inclusion, or named relations among Methods are treated as natural or inevitable and a present decision depends on how that differentiation arose. Typical questions concern why a variant appeared, why one contribution separated from another, why a provider or profession retained a form, or why a relation changed under pressure.

Begin by bounding the exact Method, established family inclusion, or relation change to explain and the decision that will use the account. Decide immediately whether the receiver needs only a dated descriptive account or intends to rely on a causal conclusion.

The first useful result can be a descriptive stop: a dated sequence with source and evidence limits. When causal reliance is live, name the causal-use question, claim kind, causality-ladder rung, and required support before constructing the explanation.

Do not use a project-local grouping label as a professional-family fact. Do not use ME.19 for decorative history, chronology, popularity ranking, or present architecture choice alone.

ME.19:0.1 - Working Distinctions

ME.19:1 - Problem Frame

An account of professional Method change relates variants recorded in successive sources to changes in institutions, tools, regulation and local Work. It examines deliberate redesign, diffusion, fashion, retention and loss. Questions about variants and selection help develop competing accounts. Process-tracing research supplies methods for examining the sequence within a case, rival explanations and diagnostic observations.

For causal reliance on either contribution, use C.28. A plausible sequence can support description and hypothesis while leaving an interventional claim unsupported. The pattern therefore separates differentiation, causal support, and current choice.

ME.19:2 - Problem

Chronology is often narrated as cause: a pressure appears, a practice changes, and the account says “therefore”. Search frequency or institutional prominence is treated as adoption evidence. Surviving versions hide abandoned variants. A project-local label is promoted into a professional family.

The downstream decision then consumes a causal premise that no identified result supports, or a useful descriptive account is discarded because it cannot prove causality.

ME.19:3 - Forces

ME.19:4 - Solution

Recover dated differentiation and rivals first. Apply the full C.28 causal-use assessment only when another decision needs a causal conclusion, and return every result with its own identity and use limit.

ME.19:4.1 - Pattern-Use Unfolding

1. Bound the explanandum. Identify one Method under A.3.1, an independently established family inclusion, or named Method relations and the differentiation to explain. A local grouping can supply candidates and questions, not the family fact.
2. Name causal use or choose a descriptive stop. State the receiver’s exact question. If causal reliance is needed, name CausalUseClaimKind, target CausalityLadderRung, comparator or intervention where applicable, and the link claims. Otherwise return dated description without causal vocabulary.
3. Establish the dated descriptive sequence. Recover source editions, Work evidence, variant appearances and disappearances, abandoned forms, and decision points. A timeline is an index, not an explanation.
4. Propose explicit link claims. Name the pressure or environmental change, affected actor or carrier, response or variation, selection or retention process, and resulting Method or relation change. Use mechanism only in a source-local sense unless an A.6.1 U.Mechanism is separately identified.
5. Generate serious rivals. Consider demand or constraint, provider/tool, regulation, authority, diffusion/fashion, recording-artifact, deliberate-redesign, and survivorship accounts where they are plausible for this history. Explain which alternatives compete and which can coexist; do not invent a demand account merely to fill a category.
6. Derive and collect diagnostic observations. Before choosing observations that are easy to collect, state which dated records, version differences, decisions, Work evidence, interviews, abandoned variants, negative cases, or cross-setting contrasts are expected under each link and rival. Preserve provenance and source dependence. Weigh the observations through :4.4 before grading the resulting claims; provenance alone does not establish diagnostic strength.
7. Run the complete C.28 boundary when needed. Issue one identifiable support result with question ref, claim kind, rung, actual evidence-path/data-regime and specialist-result refs, common-threat-screen ref, verdict, supported/unsupported causal uses, limits/window, and reopen. Raw observations or source names are not support-component results. A missing identification, bound, or estimate required for this named causal-use question, or an unresolved live threat to that use, lowers the verdict. Do not commission an estimate merely because another kind of causal question would need one.
8. Return distinguishable results. Grade differentiation claims as observed, source-supported, inferred, expert-estimated, contradicted, or missing and retain rivals. Keep the causal result separate. A downstream choice cites only causal reliance allowed by the verdict and retains its own authority. An unsupported or undecided result may not serve as positive causal evidence; a separately named non-causal observation or hypothesis may still support a bounded trial.

ME.19:4.2 - Record the Results

ME.19:4.3 - What Changes in Practice

Practitioners can use history without turning it into inevitability. A dated account can reveal forgotten variants and serious rivals; a causal stop can prevent unsupported reliance; and a current architecture decision can still authorize a reversible probe from a separate non-causal observation.

ME.19:4.4 - Weigh Historical Evidence between the Actual Accounts

A reliable source can contain a fact that all serious accounts predict. Such a fact helps establish the sequence without favoring one explanation. Conversely, a potentially revealing statement may have little weight because its date, authorship or relation to the events is uncertain. Keep these questions separate from the claim grades in :4.1.

1. Make the comparison specific. For the same finding, ask how expected it would be under each serious account, given the evidence already incorporated. Explain the difference. Compatibility with one account alone is insufficient. If two causes can operate together, compare their proposed contributions or a combined account rather than forcing an exclusive choice.
2. Examine how the finding became available. Distinguish an event from a later assertion about it. Ask what the source could observe, why it was recorded, and how it was selected and preserved. A missing record weighs against an account only to the extent that the proposed event should have produced an accessible surviving record.
3. Use additional information, not additional copies. A brochure, an interview repeating it and an article citing that interview may transmit one assertion. Assess the later item conditional on what is already known; do not count it as independent corroboration. Separately established timing or Work evidence can add information even when it appears in the same archive.
4. Return a conditional comparison. State which finding favors which account and which assumptions carry that judgement. Preserve an indistinguishable result when the accounts predict the same observations or source uncertainty defeats discrimination. Check whether the preference survives plausible changes in disputed coding, source selection, dependence or the weight given to a key finding. If it does not, make that fragility part of the result. Use numerical analysis only with a justified observation model; do not invent probabilities or turn named test types into automatic grades.
5. Reconsider the relevant evidence when the account changes. A newly discovered actor, date or mechanism may alter what earlier findings would mean. Compare the revised account with the relevant prior corpus as well as the new item, keeping source dependence visible. Do not attach the old conclusion to a newly worded hypothesis without this reconsideration.
6. Return only the supported use. The comparison can identify a promising next inquiry or a bounded historical hypothesis. When a receiver needs causal reliance, supply this contribution and its limits to C.28; the comparison alone is not its complete support result. If a revised premise matters to an existing repertoire or choice, use its evidence dependencies to identify the affected ME.2, ME.5 or ME.6 result and reassess that reliance. A change to historical attribution need not invalidate an independently qualified current Method.

ME.19:5 - Archetypal Grounding

ME.19:5.1 - Descriptive Stop

This is a constructed design-office history, not a report about a real organization. The office must reconcile names and source editions after drawing signoff differentiated. For this case, independent A.3.1 identification and ME.15 variant qualification have already established common Method M-Signoff-0 and local variants M-Signoff-E and M-Signoff-M. All return approve/reject for a drawing, but the electrical variant requires clearance and harness-revision checks, while the mechanical variant requires load-case and fit checks; each withholds approval when its required check is absent. Those reusable differences are not inferred from separate form names. No professional-family or composite-Method claim is made.

The explanandum is this local differentiation and its documented timing. The receiver needs to distinguish the introduction of the different checks from their later representation in separate electronic forms. It does not need a claim that one pressure caused the split or that either variant is better.

The case premises also admit ElectricalReviewer-E and MechanicalReviewer-M as Agents for their respective checking under A.13, and their 9 and 18 April occurrences WE7 and WM4 as Work under A.15.1. The Work enacts M-Signoff-E and M-Signoff-M, respectively; E1 and M1 are the instructions used, not the enacted Methods. The bounded source set contains these case facts:

Before inspecting the April records, the office has two serious explanations. R-demand says domain-specific omissions prompted the proposal and selection of different rules; it predicts a problem record, a response proposal, and distinct checks before the form migration. R-carrier says the apparent split is only a naming or recording effect of that migration; it predicts unchanged checks beneath the new names. R-carrier is initially plausible because the searchable PLM history starts with F2 and makes the split look like a May event.

Comparing E1/M1 and WE7/WM4 with S3 and T2 is diagnostic: different reusable checks and their enactments are recorded in April, before F2. This contradicts R-carrier’s strong claim that only names changed in May. It fits R-demand, but the available records do not settle why the office selected separate rules over common signoff with escalation, or how other pressures contributed. Missing deliberation evidence leaves that link unresolved here; a separate control office is not a universal requirement for within-case causal inquiry. A weaker carrier contribution to later retention remains possible and untested; rejecting the naming-only account does not prove its rival.

DA-Signoff-Differentiation-1 returns these grades and limits:

The receiving source-reconciliation decision can now keep E1 and M1 as different variant descriptions, keep S3 as the common predecessor account, and link F2 as their later form without dating Method differentiation from form creation. It leaves the exact first occurrence and reasons for selection unresolved. No C.28 result is created because no causal reliance is taken. Reopen the relevant date, relation, or link claim if an earlier instruction, the missing deliberation record, or contrary Work evidence appears; do not choose today’s architecture from this history alone.

ME.19:5.2 - Causal-Use Branch and Non-Causal ME.6 Consumption

The EC-417 release scenario records a cadence/evidence mismatch near several reopenings. Four result identities remain separate:

• DA-EC417-CadenceDifferentiation-1 is a partial descriptive account: the retained co-occurrences do not fill the dates, variants, and selection history needed for a complete differentiation account;
• CUR-EC417-CadenceEffect-1 is the causal-use support result;
• DC-EC417-CadenceMismatch-1 is a non-causal timing/co-occurrence hypothesis; and
• AD-EC417-B2-Trial-1 is the receiving ME.6 architecture decision.

The causal-use question CUQ-EC417-CadenceEffect-1 asks: “Would entering provisional-evidence reconciliation at D-21, rather than waiting for signed evidence at D-8, reduce mismatch-related reopenings in EC-417-like releases for this team, supplier, and change class?” Its causalUseClaimKind is causalEffectClaim; its target rung is interventionalActionRung.

The actual support-component refs are evidencePathRefs=[EP-EC417-BundleSequence-20, EP-EC417-RigAvailability-20, EP-EC417-QuarterlyCadence-2] and empiricalDataRegimeRefs=[EDR-EC417-NaturalReleaseHistory]. No identification or estimate result exists.

Common threat screen CTS-EC417-CadenceEffect-1 records:

Every live threat lowers the causal-support verdict because no specialist result closes it. The C.28 verdict is unsupported. supportedUse: no interventional causal reliance; use this result only as a stop against that reliance. unsupportedUse: claiming that cadence mismatch caused the reopenings or that B2 will reduce them. The evidence window is the named twenty releases and two earlier cases for this team, supplier, and change class. Reopen only on a governed comparison or replayable identification or bound that varies reconciliation timing while rig, approver capacity, outcome definition, and evidence access are controlled or explicitly modeled.

DC-EC417-CadenceMismatch-1 separately retains only the observed timing/co-occurrence as a trial hypothesis and design constraint. AD-EC417-B2-Trial-1 consumes that non-causal result, capacity, confidentiality, authority, and reversibility to select only a bounded B2 trial. SafetyReviewer-17 performs W-SafetyEvidenceDecision-17 under ASG-SafetyReview-17 and AUTH-SafetyEvidence-17 for the evidence-condition result; ReleaseDecider-17 separately performs W-ReleaseDecision-17 under ASG-ReleaseDecision-17 and AUTH-ReleaseDecision-17 for branch entry and release disposition. The architecture decision does not cite CUR-EC417-CadenceEffect-1 as positive causal evidence.

ME.19:5.3 - A Dated Proposal Has More Weight than Repeated Promotion

Consider a constructed extension of the signoff history. Method and variant identification remain the independent premises of :5.1. The next historical inquiry must choose between H-response, in which repeated domain-specific omissions contributed to selecting separate rules, and H-tool-only, in which a provider’s form package induced the split and the omissions were invoked afterwards. Tool support may also have helped retain a split selected for other reasons, so these are not the only possible contributions.

A newly recovered internal decision memo compares separate rules with common escalation, rejects escalation because the named specialist would not be available, and recommends separation. Its authenticated March date precedes the earliest presently documented provider contact. This combination is more expected under H-response than H-tool-only: it records a problem-specific choice and reason before the currently known tool opportunity. The weight depends on the memo’s authenticity, whether it recorded an actual decision rather than advocacy, and whether earlier provider influence remains unrecorded.

A budget approval refers to that memo. It supplies evidence that resources were authorized, but its repeated rationale is not a second independent explanation. A later brochure and three interviews all repeat the same launch narrative; they show circulation of that story, not four independent confirmations. No trial of common escalation has been found, but trial records were not routinely preserved. That absence adds little against an account in which such a trial occurred.

The investigator therefore gives H-response greater relative support than H-tool-only under the stated evidence and assumptions, while retaining possible provider influence and a mixed account. This selects a focused search for earlier contact and actual decision records. It supplies neither a numerical probability nor a claim about the effect of imposing separate rules today.

Suppose the next archive yields an authenticated February provider proposal. The earlier temporal advantage disappears. The investigator reassesses the memo and budget in light of that contact, and compares a mixed account with tool-only influence and response to omissions. The memo still records its stated reason; it no longer independently shows that this reason preceded any known provider opportunity. Revised historical attribution returns to a present repertoire or decision only where that result relied on the attribution. Existing direct evidence that a local variant works within its qualified scope remains available.

ME.19:6 - Bias-Annotation

ME.19:7 - Conformance Checklist

• The explanandum is an identified Method, established family inclusion, or named Method relation change.
• The receiving decision and exact causal use or descriptive stop are explicit.
• The dated sequence precedes explanation and keeps source editions, Work evidence, variants, disappearances, and decision points recoverable.
• Every link claim names pressure/change, affected actor or carrier, response/variation, selection/retention, and resulting Method or relation change.
• Serious rivals and diagnostic observations are derived before convenient collection.
• Diagnostic weight compares the actual rivals under stated prior evidence, source-generation conditions and dependencies; source repetition is not independent support.
• Differentiation claims carry grades and limits, and changed accounts prompt reconsideration of the relevant earlier evidence.
• Any causal-use result contains the complete current C.28 identity, support, threat, verdict, use, window, and reopen fields.
• Raw observations and source names are not presented as specialist support results.
• Differentiation, causal support, non-causal hypothesis, and downstream architecture decision remain separate.
• An unsupported or undecided result supplies no positive causal premise.

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

ME.19:9 - Consequences

Professional Method history becomes decision-usable without being made causally stronger than its evidence. Forgotten variants and rivals remain available, while current architecture choices can distinguish causal reliance from a reversible probe based on non-causal observations.

The cost is explicit result separation and threat screening. Some elegant origin stories will end as descriptive accounts, and some causal questions will remain unsupported until a stronger design or bound exists.

ME.19:10 - Rationale

Differentiation history, causal support, and present choice have different subjects and truth conditions. A dated sequence can be accurate while its causal explanation is unsupported; an unsupported causal claim can coexist with a useful non-causal design constraint; and neither supplies present authority.

The pattern connects questions about variant generation, transmission, fashion, retention and loss. Evolutionary analogies and search-frequency examples can suggest hypotheses and rivals; their causal use depends on diagnostic observations. Process-tracing sources strengthen that inquiry. C.28 states what support a causal use needs, keeping a plausible narrative separate from identification or estimation.

ME.19:11 - SoTA-Echoing

Reopen when a current source changes the diagnostic logic or causal-use rules, when a representative history cannot keep differentiation and causal support separate, or when a downstream use repeatedly needs a missing result field.

ME.19:12 - Relations

• A.3.1 governs Method identity; G.5 governs established family or selector claims; a local grouping label supplies neither.
• A.10 governs source and evidence paths; A.10.1 helps locate actual dependencies when a premise changes; C.27 governs temporal-claim adequacy; C.28 and C.28.CM govern causal-use support and construction of causal inquiry.
• ME.2 may retain variants and lineages without inheriting causal truth.
• ME.6 may consume the differentiation account, causal-use verdict, or separately named non-causal observation only within each result’s use boundary and keeps its own authority.
• Cultural continuation and professional-history uses remain separate from one current project architecture decision.

ME.19:End

ME.2 - Recover a Reusable Method Repertoire and Its Lineages

Primary working result: one inspectable Method repertoire for a named use that keeps identified Methods, candidate Method accounts, MethodDescriptions, source contributions, family or local-grouping claims, variants, supported lineage relations, evidence limits, source editions, and missing positions distinct.

ME.2:0 - Use This When

Use this pattern when a one-Method, plurality, or Method-relation focus needs alternatives, variants, evidence, and provenance that another practitioner can inspect and reuse. Typical uses include comparing several Methods, forming a project proposal, locating a variant, or checking whether a familiar source contribution still supports the current question.

Begin with the named comparison or proposal use, the focus result or equivalent subject statement, and the practical result the project needs. Search primary Method Engineering sources and sources from the practice that owns that result. Keep exact editions and status visible while assembling the smallest repertoire that can support the use.

The first useful result is a set of status-preserving entries with claim-bearing source material, supported relations, evidence limits, currentness, and explicit missing positions. An honest gap is part of the repertoire when it changes comparison or proposal work.

Do not treat a bibliography, repository, package outline, observed Work, or list of popular names as a Method repertoire by itself. Co-listing supplies neither Method identity nor an established family, and documented lineage supplies neither superiority, causation, composition, nor present applicability.

ME.2:0.1 - Working Distinctions

ME.2:1 - Problem Frame

A project rarely receives a clean inventory of Methods. It receives old procedure editions, package sections, conference descriptions, local checklists, tool configurations, retrospective accounts, and claims that one practice “came from” another. The most familiar names can hide the best-supported contribution, while a well-stocked repository can hide a decisive gap.

Method Engineering sources encourage reuse from method bases and situational construction. Engineering-design sources add intended use, representation, procedure, tool, and ecosystem questions. Those source lines improve search and recovery, but their local elements are not automatically FPF kinds. The repertoire must therefore preserve what each source actually contributes while keeping Method, account, description, Work, family, grouping, and lineage claims separate.

ME.2:2 - Problem

Three shortcuts make a repertoire unusable. First, every package item is called a Method. Second, co-listing or a common ancestor is called an established Method family. Third, the newest source edition silently replaces older evidence even when the current use still relies on an earlier claim or the changed edition has not been checked.

The resulting list appears complete but cannot answer which alternatives are identified Methods, which are only accounts, why a relation is believed, what changed between editions, or which missing position blocks the next decision.

ME.2:3 - Forces

ME.2:4 - Solution

Build the repertoire around one receiving use. Recover exact subjects and source contributions, qualify every relation by its own evidence, and record unsupported positions as gaps instead of filling them with guesses.

Recognition is cheap: a source or repository entry is worth inspecting when it may supply a relevant alternative, contribution, or missing relation. Assurance begins only when a decision relies on the row; then its subject status, exact source edition, evidence, relation basis, currentness, and limit must support that use.

ME.2:4.1 - Pattern-Use Unfolding

1. Bind the repertoire use. Name the focus, receiving result, decision, situation family, and what the next comparison or proposal must inspect. State what would make an entry relevant.
2. Search both source lines. Search primary Method Engineering sources for reusable approaches and source organization, and search the problem-owning practice for Methods, accounts, variants, evidence, and current operating constraints. Record exact source editions or dates and the claim-bearing passages or artifacts used.
3. Recover subjects before grouping them. Cite the existing A.3.1 identity result for every identified Method. Keep provisional material as a candidate Method account. Attach a MethodDescription only to its already identified Method. Keep tools, roles, capabilities, support arrangements, evidence, and Work occurrences under their actual kinds.
4. Extract contributions with limits. For every useful source, state the contribution used, the subject it concerns, its evidence or status, its scope, and what it does not establish. A package position or source vocabulary does not determine the FPF kind.
5. Record relations independently. Separate established family membership, project-local grouping, variant claims, input/result relations, and supported lineage relations. For lineage, name both exact subjects, the relation claimed, and the source that supports it. Leave same-Method identity, causal effect, superiority, and composition open unless their own governors settle them.
6. Pin editions and use-qualified currentness. Distinguish publication or artifact edition from the claim relied on for the current use. Keep its relevant conditions and actual evidence, permission or qualification windows; identify the changed premise that would require reconsideration. A new edition or review date can invite attention without defeating that claim. Use a broader G.2 SoTA pack only when the use needs refreshable multi-source synthesis rather than a small question-relative source set.
7. Expose missing positions. List absent alternatives, unknown editions, unsupported ancestry, missing evidence, unresolved family status, and contributions whose source meaning cannot yet be recovered. Say which next use each gap blocks or merely weakens.
8. Return the bounded repertoire. Publish the subject inventory, source-contribution rows, relation rows, currentness limits, and gaps for the named use. Stop when the next decision can inspect the live alternatives and uncertainties without guessing their status.

ME.2:4.2 - Record the Result

ME.2:4.3 - What Changes in Practice