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

Name used here	Meaning
named-use repertoire	The smallest inspectable result that exposes subjects, statuses, claim-bearing sources, relations, limits, and gaps for one comparison or proposal use. It is not every item in a repository.
identified Method	A reusable world-side way of doing already identified under `A.3.1`. Repertoire inclusion does not repeat or strengthen that identity.
candidate Method account	A provisional claim-bearing episteme about a possible Method. Repertoire inclusion preserves its unresolved identity conditions.
MethodDescription	A description of one already identified Method under `A.3.2`, kept distinct from that Method, candidate accounts, and Work occurrences.
source contribution	The exact claim, distinction, procedure cue, evidence item, or representation taken from a named source edition for the current use, together with its limit.
established family relation	A classification or membership relation supported under its independent governor. A family label or repertoire row does not establish it.
project-local grouping	A named set assembled for one local comparison or selector use, with its criterion and unresolved family status explicit.
variant claim	A claim that two practices, accounts, descriptions, or editions differ in a named way. Calling them variants does not decide whether they are the same Method.
supported lineage relation	A source-backed relation such as edition succession, documented derivation, adoption, or adaptation between exact subjects. It records provenance, not causal effect or merit.
missing position	A subject, relation, edition, evidence item, or provenance link needed by the named use but not currently supported.

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

Force	Tension
Reuse	A repertoire should save future search, while a universal catalogue accumulates irrelevant and stale entries.
Breadth	Important alternatives may sit outside Method Engineering literature, while undirected collection becomes a bibliography.
Stable reference	Exact identities and editions aid replay, while practices and descriptions continue to change.
Lineage	Provenance explains where a contribution came from, while ancestry is easily overread as causation, quality, or family membership.
Honest incompleteness	Missing positions should remain visible, while teams are tempted to fill them with plausible names or inferred relations.
Local comparison	A temporary grouping can make a decision tractable, while its label can be mistaken for a world-side family.

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

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.
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.
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.
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.
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.
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.
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.
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

Result position	Required content
repertoire use	Focus, receiving result, situation family, consuming comparison or proposal, relevance criterion, and scope.
subject inventory	Exact Method identities, candidate-account refs, MethodDescription refs, and unlike supporting subjects kept outside the Method rows.
source contributions	Exact source/artifact edition, claim-bearing contribution, subject, evidence/status, scope, and limit.
relations	Established family basis if any, local grouping criterion, variant claims, supported lineage relations, and other decision-bearing relations with truth status.
currentness	Publication/artifact edition, relied-on claim and receiving conditions, actual time boundary where one applies, and the material change that would reopen this use. No expiry date or refresh plan is required solely to complete this position.
missing positions	Missing subject, provenance, relation, edition, evidence, or source meaning and its effect on the named use.
stop and next use	What the repertoire supports now, what it does not establish, and which gap or source change reopens it.

ME.2:4.3 - What Changes in Practice

Teams stop searching a repository as though every file were a reusable Method. They can compare identified Methods alongside promising accounts without promoting either, trace a proposal to exact contributions without asserting composition, and stop with a useful gap instead of inventing a complete lineage.

ME.2:5 - Archetypal Grounding — EC-417 Release-Evidence Repertoire

The EC-417 project needs an inspectable repertoire for a Method-relation comparison around one safety-relevant controller release. The relevance criterion is narrow: an entry must contribute to verification, integration, supplier evidence, release authority, or evidence reconciliation for the named receiving result. The following identifiers and editions are local scenario records; they are not population evidence.

Subject and status	Claim-bearing basis and edition	Supported relations or lineage	Use limit or missing position
`M-HW-Verify`, identified Method	existing `A.3.1` identity result; hardware-verification procedure `HV-6`; EC-417 verification records	its verification result is an established input to release authorization for this use	no supported lineage to another Method and no general effectiveness claim beyond the cited use window
`M-SW-Integrate`, identified Method	existing `A.3.1` identity result; firmware-integration procedure `FI-4.8`; integration records	description edition `FI-4.8` succeeds `FI-4.7`; this is document-edition lineage, not a claim that the Method became a different or better Method	transfer beyond controller firmware `4.8` and the named toolchain is untested
`M-Supplier-Approve`, identified Method	existing `A.3.1` identity result; supplier pinout-approval procedure `H17-3`; signed approvals and missing-approval stops	signed or explicitly missing approval supplies an input/stop to the release decision; `H17-3` documents an adaptation from `H17-2`	whether the documented adaptation changed Method identity is unresolved
`M-Release-Authorize`, identified Method	existing `A.3.1` identity result; release checklist `RC-17.3`; named authorization results	consumes verification, evidence-state, and authority conditions for EC-417	no family relation with the other three Methods is established
`C-Evidence-Reconcile-Internal`, candidate Method account	eight internal cases in evidence dossier `ER-EC417-12+1`	documented derivation from the eight internal occurrences and their artifact traces	`A.3.1` identity and transfer to supplier-originated changes remain open
`C-Evidence-Reconcile-Supplier`, candidate Method account	four supplier-originated cases plus the held-out thirteenth case in `ER-EC417-12+1`	documented derivation from those cases; the held-out case supports the supplier branch without proving a Method	`A.3.1` identity, population scope, and relation to the internal account remain open
`C-AI-Trace-Review`, human-governed candidate Method account	AI trace prompt `ATP-2`, confidentiality rule, human-decision record set `HDR-TraceAcceptReject-17`, and decision-result set `RES-TraceAcceptReject-17`	`ATP-2` contributes prompt-and-guard description content to the candidate account; `HDR-TraceAcceptReject-17` evidences the bounded human Work set `W-TraceAcceptReject-17` performed by `TraceReviewer-17` and links each occurrence to its corresponding result in `RES-TraceAcceptReject-17`; the candidate account is documented as derived from `ATP-2`, `HDR-TraceAcceptReject-17`, and `RES-TraceAcceptReject-17`; the AI provider remains a separate System	no evidence of autonomous authority, effectiveness, or transfer outside the named information boundary; none of these relations establishes Method identity, family membership, causation, superiority, applicability, or composition

For the D-21 through D0 use window, the project relies on the exact contributions and conditions in the table. If a new export or edition changes only their layout while the relied-on claims, configuration, access and use remain the same, retain the repertoire without a new search, trial or renewal record. If FI-4.8 instead loses coverage for a changed controller or toolchain, or an actual permission or qualification window ends, reopen or suspend that affected use even before the planned review date. Keeping the old edition identified does not authorize continued reliance on defeated premises. Reconsider only the affected source-use row, preserve the earlier claim for its supported conditions, and keep the needed limitation with the result for later receivers.

The existing project-local locator LG-EC417-ReleaseMethods contains only the four identified Methods for the bounded release comparison. Its criterion is contribution of a verification, integration, supplier-approval, or authorization result to EC-417. The three candidate accounts remain adjacent repertoire entries with their own statuses; a wider source-inspection list does not silently add them to the Method grouping. Family status remains unresolved. No family membership, fifth Method, or composite Method follows.

Description-side material stays separate. Existing A.3.2 results identify HV-6, FI-4.8, H17-3, and RC-17.3 as MethodDescriptions of the four already identified Methods. The stage table, bundle records, AI prompt, and evidence grades remain other claim-bearing epistemes or artifacts. They are not additional Methods. The two reconciliation records and the AI review record remain candidate accounts, so no A.3.2 MethodDescription is asserted for them.

Proposed-whole account C-EC-Release-v2 is recorded outside the repertoire membership table as an architecture subject. It cites contributions from the four Methods and three accounts, but that source relation establishes neither a whole Method nor methodPartOf.

The repertoire stops honestly with four missing positions: no established Method family covers the local grouping; no source establishes a Method-lineage relation among the four identified Methods; the same-Method or distinct-Method relation between the two reconciliation accounts is unresolved; and the AI account lacks transfer and effectiveness evidence. Those gaps do not prevent ME.5 from qualifying individual subjects or ME.6 from comparing named structures. They prevent family, ancestry, superiority, and composite claims.

ME.2:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
repository-completeness bias	A large collection is treated as a complete repertoire.	Bind relevance to one use and list missing positions explicitly.
package-kind bias	Sections, tools, roles, and artifacts are all called Methods.	Recover each subject’s actual kind or provisional status before grouping.
lineage-progress bias	A later edition or descendant is assumed better or more effective.	Record only the supported provenance relation; evaluate worth and causality separately.
family-by-co-listing bias	Entries under one heading become a Method family.	Cite the independent family basis or call the result a project-local grouping.
freshness-by-date bias	The newest publication is assumed applicable to the current use.	Separate source edition, source-use currentness, evidence window, and applicability.

ME.2:7 - Conformance Checklist

The repertoire has one named comparison or proposal use and a relevance criterion.
Every Method cites an existing A.3.1 identity result; every provisional subject remains a candidate account.
MethodDescriptions attach only to already identified Methods and remain distinct from those Methods.
Every source contribution names an exact source or artifact edition, subject, contribution used, evidence/status, scope, and limit.
Established family relations, project-local groupings, variant claims, and lineage relations are recorded separately.
Every lineage claim names both subjects, the relation, and the supporting source without implying causation, superiority, or composition.
Publication/artifact edition and current project reliance are distinguishable. A new date alone neither defeats nor renews support; changed evidence, applicability and actual time boundaries still govern the receiving use.
Missing alternatives, provenance, relations, editions, evidence, or source meanings remain visible.
The stop states what the repertoire supports and which claims remain unavailable.

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

Anti-pattern	Repair
“The repository contains 40 Methods.”	Reclassify exact entries; count only Methods already identified under `A.3.1`.
“These practices share a history, so they form one family.”	Separate the supported lineage relation from the independently governed family question.
“Version 3 supersedes version 2, so it is better.”	Record edition succession and compare the decision-bearing contribution under its own evidence.
“We observed the procedure, so the Method belongs in the repertoire.”	Keep the observation as occurrence evidence or a candidate account until Method identification.
“A blank row makes the repertoire incomplete and unusable.”	Name the missing position and whether it blocks, weakens, or does not affect the receiving use.

ME.2:9 - Consequences

The project gains reusable alternatives with recoverable provenance, bounded evidence, and visible gaps. Later qualification and architecture comparison can inspect the same subjects without repeating search or inheriting false family and composition claims.

The cost is a smaller catalogue. Some lineages remain partial, and the newest source may be unusable until its changed meaning or applicability is checked.

ME.2:10 - Rationale

A repertoire becomes reusable when its users can distinguish statuses and trace provenance. Source lineage can explain where an edition, account, or variant came from, but it cannot answer whether a Method exists, whether two Methods form a family or whole, whether one caused an outcome, or whether the latest variant is preferable. Those questions have different subjects and governors.

The repertoire distinguishes Methods, performed Work, descriptions, variants, capability and tools, including cases where several representations concern the same Method. These distinctions keep a source document’s organization from determining the kind of thing each passage describes. Method Engineering literature supplies search and reuse practices; FPF supplies the status and relation boundaries needed to use their contributions across projects.

ME.2:11 - SoTA-Echoing

Source	Retained contribution	Use boundary
Henderson-Sellers and Ralyté, Situational Method Engineering: State-of-the-Art Review	Method-base lineage, reusable source material, situational construction, and explicit Method Engineering traditions.	Source-local fragments and construction terms do not determine FPF kinds, family membership, or composition.
Gericke, Eckert, and Stacey, Elements of a design method	Method ecosystem, core idea, representation, procedure, intended use, tool, and adaptation questions.	The elements guide source recovery; they are not an imported ontology or universal repertoire schema.
Current FPF `G.2`, `G.5`, and `G.11`	Refreshable SoTA sourcing when needed, truthful family or local set results, and edition/currentness discipline.	These patterns do not identify repertoire Methods or turn co-listing and lineage into selection, family, or merit.

Reopen when a relied-on source contribution, its support or its applicability changes, a missing position becomes available, an A.3.1 result changes a subject’s status, a family or lineage relation gains or loses support, or the named comparison requires an alternative outside the current relevance boundary. Age or edition succession alone establishes none of these changes.

ME.2:12 - Relations

ME.1 or an equivalent result supplies a one-Method, plurality, or Method-relation focus and its statuses. ME.2 may also start from another receiving use that meets the same conditions.
A.3.1 governs Method identity; A.3.2 governs MethodDescriptions. Repertoire inclusion changes neither.
G.2 supplies a broader refreshable SoTA pack only when that heavier source result is needed; G.11 governs an applicable currentness question without requiring refresh Work or a waiver for continued applicability; G.5 supplies governed family or selected-set results when its entry conditions hold.
ME.4 may recover decision-relevant entries from a heavyweight package. ME.18 may supply scoped candidate accounts. Use either only when its result is needed.
ME.3 may use the repertoire to expose situational criteria; ME.5 receives identified Methods and candidate accounts with their source limits; ME.6 receives only named structures and relation questions.
ME.7 may cite repertoire contributions for a proposed-whole account, but citations create neither a whole Method nor obtaining composition.