Recover Method Contributions from Documentary Sources
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
Use this when. A methodology, standard, body of knowledge, maintained synthesis, reference model, or tool suite mixes reusable ways of doing with descriptions, Systems, capabilities, evidence, authority, and support. The receiving decision needs contributions from one package or several documentary sources, but their chapters and component lists do not establish Method structure.
Relations
Content
Problem Frame
Use this when. A methodology, standard, body of knowledge, maintained synthesis, reference model, or tool suite mixes reusable ways of doing with descriptions, Systems, capabilities, evidence, authority, and support. The receiving decision needs contributions from one package or several documentary sources, but their chapters and component lists do not establish Method structure.
Begin with one receiving decision and the exact source edition or snapshot. For several sources, keep each source's role and recovery scope visible. Recover only contributions and dependency slices that can change the decision; completeness is relative to this boundary.
The first useful result is a source-traceable Method-recovery dossier. Identified Methods and individually scoped candidate accounts can proceed to A.3.1.QM with their support and evidence limits. A proposed whole proceeds to B.1.5.CM when its identity and relations are the question. Tools, descriptions, capability, authority, and other useful contributions remain available under their kinds.
Ordinary non-use. Do not decompose an already precise Method to populate a library or inventory material whose presence cannot change the receiving decision. If records, interviews, traces, or observations are offered as evidence from which a reusable way must be reconstructed, use A.3.1.MR; enter specialist RMP.10 only when its additional evidence programme is needed.
A document can contain both prescribed guidance and testimony about performance: route the selected contribution by its use, not by its file extension.
Working Distinctions
Heavyweight packages connect concerns through publication, pedagogy, institutional history, tools, or viewpoints. Their visible organization may differ from Method, Work, subject, description, capability/provider/support, allocation, or cultural structures.
Method Content Theory and design-Method element research contribute questions about goal, procedure, rationale, framing, mindset, representation, intended use, and tools. Keep the answers with the Method, candidate account, description, capability, support relation, cultural claim, or other subject they concern. Several sources can ask similar questions without giving the same answer.
Problem
Copying package headings into a Method library can misidentify the contributions. A role becomes a Method, a checklist becomes a component, a tool becomes a participant Method, and adjacency becomes methodPartOf. The opposite error extracts a procedure alone and loses the rationale, input/result correspondence, authority, evidence, or support condition that makes it usable.
A later qualification then appears precise but cannot be replayed from the source and cannot distinguish a Method defect from missing access, capability, evidence, or authority.
Forces
Solution
F.0.1 supplies source-local meaning recovery; A.3.1.MR instead reconstructs a candidate reusable way from Work evidence. The documentary operation below retains what an author proposes, including the source's complete constructive scope where that is the requested result. It does not convert a documentary assertion into an observation of practice.
Build a source-traceable dossier around the receiving decision. Recover each documentary contribution in its own source meaning, preserve unlike kinds, and prepare only the downstream subjects needed for the receiving decision.
Pattern-Use Unfolding
-
Bound the receiving use and sources. Name the decision, relevant viewpoint, scope, and exclusions. For each documentary source give its exact edition or snapshot, source-return locator, role in this use, selected recovery profile, and currentness or reopening condition. One package normally needs one compact source/use statement, not a separate register.
-
Choose how much to recover. Use the profiles below. A maintained source's source-local recovery and comparison with current alternatives answer different questions; do not let the comparison erase a source contribution before it has been understood.
-
Read source meaning before placement. For each selected contribution retain the source term and locator, difficulty or opportunity, any asserted reusable action or change, any first useful result or blocker, and receiving use. Keep its original status, limits, purpose, and explicit or implied relations. A source ambiguity remains an ambiguity.
-
Preserve the subject and evidence role. Distinguish identified Methods, individually scoped candidate accounts, MethodDescriptions or other epistemes, Systems and support/access, capabilities and assignments, inputs/results/premises, and direct relations. A source's report of evidence is recovered as that report, not as independently established Work or effectiveness. Send a new question about a reusable way in occurrence evidence to A.3.1.MR; specialist RMP.10 follows only under its entry condition.
-
Record intended use and possible loss. Say what the receiving use proposes to keep, change, reject, or leave unresolved and what source meaning or context would be lost. These are source-local recovery dispositions. Do not yet assert cross-source sameness, perform semantic merging, allocate a remainder to a supplier, or design the resulting pattern language.
-
Recover direct relations and small dependency slices. Retain supported production/use, schema correspondence, provider access, allocation, responsibility, authority, or other relevant relations. A line, container, chapter, lane, or local section supplies no relation. Attach only the source claims, conditions, and returns needed for the next judgement.
-
Prepare the downstream subjects. A.3.1.QM receives only identified Methods and individually scoped candidate Method accounts, each with the smallest slice needed to judge contribution, inputs/results, applicability, burden, capability, support, authority/access, and evidence.
B.1.5.CM receives a proposed-whole account when whole identity and relations are the question; retain its proposed semantics, participant statuses, relation boundary, and source slices. Other kinds remain in the dossier or accompany those subjects without becoming Methods.
-
Return the dossier and any blocking gaps. Use open navigation sections when they help retrieval. Stop when the subjects and source basis needed for the receiving decision are recoverable. If edition, role, receiving use, a needed current comparator, source return, kind, relation, or evidence is missing, name the affected contribution and the missing basis. Continue unaffected recovery when it can still serve the receiving decision; do not claim completeness beyond the recovered boundary.
Select the Recovery Profile Per Source
For an ordinary package, the default is decision-bounded recovery: inspect only source claims and dependency slices that can change the receiving decision. This default needs neither maintained-synthesis status nor a prior supplier comparison. Select a specialized profile below only when its condition holds; naming a profile does not itself add a recovery operation or a record.
“Full” is not an instruction to extract all possible knowledge from a source. The receiving decision sets the completeness boundary. A change from source-local recovery to cross-source reconciliation is a new question, not the final step of A.3.1.DR.
Record the Result
Keep these distinctions in the dossier already being used; they are not a requirement for one file or row per field. A short one-source result can carry the source/use statement in its opening sentence.
What Changes in Practice
Practitioners can reuse a Method, retain a candidate account, cite a description, require a capability, preserve an authority stop, or depend on a System without importing a package as a Method whole. A plural dossier also shows why each source was inspected and how far its contribution reaches. Later qualification stays small and source-recoverable; later reconciliation can distinguish a real disagreement from unlike source roles.
Archetypal Grounding — EC-417 Release Assurance Package
For this constructed case, take the listed EC-417 package contents as one fixed documentary snapshot. Use it as Method guidance for the changed release decision, recover the decision-bearing slice, and return when the package, receiving use, or a relied-on condition changes. This supplies the source/use boundary for the one-source case.
The EC-417 team receives a “release assurance methodology” containing a stage table, release checklist, supplier procedure, AI prompt, PLM and CI instructions, test-rig guidance, role descriptions, and stored evidence bundles. The receiving decision is whether its Method contributions and candidate reconciliation accounts can support a changed release arrangement.
The dossier uses open sections but preserves unlike kinds:
Two example dependency slices show why the full package is neither copied nor discarded:
M-HW-Verifytravels with its change input, verification-result meaning, rig condition, hardware capability, procedure provenance, and evidence window.C-Evidence-Reconcile-Suppliertravels with the supplier procedure, signed-evidence condition, supplier-configuration responsibility, closure authority, four observed source cases, and the unresolvedA.3.1identification question.
The supplier procedure's four reported cases remain a documentary source claim and evidence return in this recovery. Inspecting the underlying occurrence records to reconstruct a reusable way is a separate A.3.1.MR question.
The four identified Methods and the three individually scoped candidate accounts are potential A.3.1.QM subjects for this use. PLM, rig, competence, authority, schema, evidence, and descriptions remain in their slices under their own kinds. C-EC-Release-v2 remains a proposed-whole candidate account and may later be resolved by B.1.5.CM; its presence in the package creates neither a fifth Method nor methodPartOf facts.
Two Documentary Roles and an Interview
This constructed case concerns a change to the release-assurance arrangement. Handbook H, edition 3, section 4, is an accepted maintained synthesis for reconstructing the supplier-evidence practice. Comparison C, edition 2, section 2, is the current comparator for the same receiving decision. Interview I, recorded on day D1, is offered as evidence about what happened during one release. These are local scenario references.
The first result is the two-source documentary dossier plus the occurrence-evidence return, not a merged release Method. When the receiving decision needs a semantic comparison, examine whether the two documentary contributions overlap, conflict or complement one another; leave unresolved relations explicit.
If C's full argument becomes unavailable but a page-located excerpt remains, retain the excerpt and reopen only entries whose receiving use depends on the missing context. H's independent source-local result remains usable. Do not turn unavailable support into proof that C was false, or continue a gap-only recovery without its baseline.
Bias-Annotation
Conformance Checklist
- The dossier names one receiving decision and an exact documentary source boundary, with each relied-on edition or snapshot recoverable.
- Each source has a use-changing role, recovery profile, source return, and currentness/reopening condition; the one-source case needs only a compact statement.
- Occurrence-evidence recovery remains with A.3.1.MR and conditional RMP.10; returned evidence limits and lower results are preserved.
- Source-local recovery stops before cross-source sameness, semantic merging, supplier allocation, or pattern-language design.
- Every selected entry retains its source locator, source meaning, existing kind or unresolved status, bounded use, and loss.
- Navigation sections can be added, split, or omitted; membership in one does not establish a type.
- Every direct relation has a source or evidence basis independent of layout.
- Identified Methods and candidate accounts are distinguishable from descriptions, Systems, capabilities, assignments, evidence, and relations.
- Every A.3.1.QM subject carries the smallest provenance-preserving dependency slice needed for judgement.
- Missing source access, kind, relation, or evidence remains visible.
- No package, chapter, list, view, or section creates Method candidacy, family membership, composition, or
methodPartOf.
Common Anti-Patterns and How to Avoid Them
Consequences
The package becomes selectively reusable while its provenance and the kinds of its contributions remain explicit. Later qualification can inspect one Method or account together with the dependencies that make its use meaningful.
The cost is explicit kind and relation recovery. Important support, authority, or evidence conditions may become more visible than the source's headline procedure.
Architectural Rationale
A heavyweight package is a publication and practice carrier, not evidence that its visible organization is a Method structure. Preserving unlike kinds lets several useful representations coexist without forcing one-to-one correspondence among Method, Work, subject, description, capability/provider/support, allocation, and cultural structures.
The dossier is open. Its value lies in tracing source contributions to the receiving decision and retaining their dependency slices, not in a fixed number of sections or a universal element taxonomy.
SoTA-Echoing
Revisit the recovered dossier when a source or package case exposes a decision-bearing contribution whose kind, provenance, role or relation remains unclear; when a selected recovery profile omitted a material receiving condition; or when the dossier imposes work that its receiving use does not need.
Relations
- A.3.1.MR governs candidate recovery from occurrence evidence; RMP.10 supplies its specialist continuation only when needed. Documentary claims about evidence remain distinct from those recovery results.
- Cross-source reconciliation and allocation consume the dossier later. A.3.1.DR preserves the inputs and return paths but does not settle that next semantic question.
A.3.1governs Method identity;A.3.2governs MethodDescription claims;B.1.5governs Method composition;F.18governs durable name claims.- C.39.MF supplies the focus and receiving decision when package recovery is the chosen next result. C.39.RP may supply an inherited repertoire or source lineage.
- A.3.1.QM receives identified Methods and individually scoped candidate accounts with provenance-preserving dependency slices. It does not receive the local navigation sections as types or a proposed whole merely because the package presents one.
- C.32.MWA.PP receives only a several-structure synthesis question that remains after individual qualification.
- B.1.5.CM receives a proposed whole account when its identity and relations must be resolved.
A.3.1.DR:End
Last Updated: 2026-10-12 — this section last modified in upstream FPF commit 6c31cd80 (github.com/ailev/FPF)