Organize a Repertoire for Method Development
About this pattern
This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.
How to use this pattern
Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.
Type: Method pattern Status: Stable
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.
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 supports the current question.
Relations
Content
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 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 the practice that owns that result; add primary Method-construction and reuse sources when their contribution can change the repertoire. Keep editions and status visible while assembling a repertoire sufficient for the use. Reuse an adequate repertoire whose grounds apply.
The first useful result is a set of status-preserving entries with claim-bearing source material, supported relations, evidence limits, currentness, and missing positions. A 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.
Working Distinctions
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 contributes while keeping Method, account, description, Work, family, grouping, and lineage claims separate.
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 replaces older evidence even when the current use 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.
Forces
Solution
A repertoire here serves a named Method-development use. G.5 supplies a Method-family registry or selector-facing result when that question is current; G.11 governs a refresh that its entry makes necessary. The construction below recovers the source contributions, alternatives and practical conditions that those results do not supply merely by listing Methods.
Build the repertoire around one receiving use. Recover subjects and source contributions, qualify every relation by its 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, source edition, evidence, relation basis, currentness, and limit must support that use.
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 the contributing source lines. Search the problem-owning practice for Methods, accounts, variants, evidence, and current operating constraints. When constructing, adapting or reusing ways of working is unresolved, include primary Method Engineering sources for the relevant construction and source-organization contribution. A sufficient domain repertoire needs no additional literature pass solely because its subject is a Method.
Record source editions or dates and the claim-bearing passages or artifacts used.
-
Recover subjects before grouping them. Cite the existing
A.3.1identity 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 kinds. -
Extract contributions with limits. For every useful source, state the contribution used, the subject it concerns, its evidence or status, its scope, and any material limit on its use. 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 subjects, the relation claimed, and the source that supports it. Leave same-Method identity, causal effect, superiority, and composition open unless their 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 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.2SoTA 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. Make the subjects, source contributions, relations, applicable conditions and any gaps available for the named use. Reuse an adequate existing account; publish a separate record when later receivers need one. Stop when the next decision can inspect the live alternatives and uncertainties without guessing their status.
Record the Result
The following positions can organize a record when one is needed. Include only relations and gaps relevant to the use; the table does not require an unsupported relation or missing position to exist.
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 contributions without asserting composition, and stop with a useful gap instead of inventing a complete lineage.
Archetypal Grounding — EC-417 Release-Evidence Repertoire
The EC-417 project needs a 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.
For the D-21 through D0 use window, the project relies on the 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 a 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 statuses; a wider source-inspection list does not 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 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 A.3.1.QM from qualifying individual subjects or C.32.MWA.PP from comparing named structures. The repertoire alone does not support family, ancestry, superiority or composite claims; a claim needed by the receiving use requires its basis.
Bias-Annotation
Conformance Checklist
- The repertoire has one named comparison or proposal use and a relevance criterion.
- Every Method cites an existing
A.3.1identity 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 a 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 time boundaries 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.
Common Anti-Patterns and How to Avoid Them
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.
Recovering subjects and provenance takes work. Some lineages remain partial, and a new source whose changed meaning or applicability is unresolved may be unusable for the affected claim.
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.
SoTA-Echoing
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.
Relations
- C.39.MF or an equivalent result supplies a one-Method, plurality, or Method-relation focus and its statuses. C.39.RP may also start from another receiving use that meets the same conditions.
A.3.1governs Method identity;A.3.2governs MethodDescriptions. Repertoire inclusion changes neither.G.2supplies a broader refreshable SoTA pack only when that heavier source result is needed;G.11governs an applicable currentness question without requiring refresh Work or a waiver for continued applicability;G.5supplies governed family or selected-set results when its entry conditions hold.- A.3.1.DR may recover decision-relevant entries from a heavyweight package. An applicable research Method may supply scoped candidate accounts. Use either only when its result is needed.
- C.39.RQ may use the repertoire to expose situational criteria; A.3.1.QM receives identified Methods and candidate accounts with their source limits; C.32.MWA.PP receives only named structures and relation questions.
- B.1.5.CM may cite repertoire contributions for a proposed-whole account, but citations create neither a whole Method nor obtaining composition.
C.39.RP:End
Last Updated: 2026-11-12 — this section last modified in upstream FPF commit 1e57ccda (github.com/ailev/FPF)