ME.4 - Recover Methods and Decision-Relevant Contributions from Documentary Packages and Corpora

Primary working result: a Method-recovery dossier whose entries retain their existing kinds or ordinary statuses, provenance, source meaning, viewpoint, bounded use, and decision-bearing relations. For qualification, ME.5 receives only identified Methods and individually scoped candidate Method accounts; ME.7 receives a proposed-whole account when whole identity and relations are the question.

ME.4:1 - 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 ME.5 with their support and evidence limits. A proposed whole proceeds to ME.7 when its identity and relations are the question. Tools, descriptions, capability, authority, and other useful contributions remain available under their actual 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 ME.18 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.

ME.4:1.1 - Working Distinctions

Name used here	Meaning
documentary source boundary	The exact package, edition, snapshot, or bounded corpus from which the receiving use recovers claims. It establishes no Method whole.
documentary role	How this source may contribute now: for example, a current comparator, maintained synthesis, normative statement, historical account, Method claim, or worked example. These are source-use descriptions, not FPF kinds.
recovery profile	How much source-local recovery the use needs. It differs from what the source is evidence for.
dossier entry	One source-traceable contribution retaining its existing kind or ordinary unresolved status.
source meaning	What the selected source says or uses the contribution to do, before local adaptation or cross-source comparison.
bounded use	The receiving decision, scope, conditions, and claim for which the contribution is recovered.
decision-bearing relation	A direct relation whose truth changes whether or how the contribution can be used.
provenance-preserving dependency slice	The smallest set of source claims, descriptions, inputs/results, support, evidence references, and relations needed to judge one Method or candidate account.
navigation section	An open reading aid, such as “Methods and accounts” or “Systems and support”; membership creates no type.

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 actually concern. Several sources can ask similar questions without giving the same answer.

ME.4:2 - Problem

The common decomposition error copies package headings into a Method library. 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.

ME.4:3 - Forces

Force	Tension
Recoverability	A later decision needs source meaning and provenance, while copying the whole package hides the load-bearing slice.
Ontological precision	Entries have unlike kinds, while one local dossier must remain readable.
Package cohesion	Source relations can matter, while package position and visual nesting supply no relation by themselves.
Affordability	A complete inventory feels safe, while decision-irrelevant entries add cost and false completeness.
Adaptation	A source contribution may be useful under changed conditions, while adaptation must not rewrite what the source claimed.

ME.4:4 - Solution

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 whose question is current.

ME.4:4.1 - 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, asserted reusable action or change, 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 ME.18 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 actual downstream subjects. ME.5 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. ME.7 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 or the first blocking gap. Use open navigation sections when they help retrieval. Stop when the receiving decision can recover its subjects and source basis. 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. Do not manufacture corpus completeness.

ME.4:4.1.1 - 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.

Profile	Select when	Recovery and limit
SoTA-first	Current alternatives can change which contributions the receiving decision needs.	Establish the relevant current comparison through ME.2 or the direct source route, then recover its decision-bearing claims. “Recent” alone is not a qualification.
Full source-local	An accepted maintained synthesis must remain reconstructable within a named scope.	Recover every decision-bearing contribution in that scope before later filtering. Preserve unsupported or non-selected material through source returns; do not import the source ontology or every chapter as a Method.
Gap-only	An exact earlier source/supplier comparison and its affected gap or delta are recoverable.	Recover that gap and its dependencies. Widen or stop if the baseline, scope, or source meaning has changed. A missing keyword is not a gap definition.
Mixed	The bounded corpus contains sources with different roles or recovery needs.	Apply the appropriate profile separately to each documentary source. Route occurrence evidence separately and retain the limits of any returned candidate account, specialist dossier, or lower result.

“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 unspoken step of ME.4.

ME.4:4.2 - Record the Result

Dossier position	Required content
recovery boundary	Receiving decision, source set and exact editions/snapshots, viewpoint, scope, and exclusions.
source/use statement	Per source: locator, role, recovery profile, receiving use, and currentness or reopening condition; combine this with the boundary for one ordinary package.
entries	Local reference, source locator and meaning, difficulty/opportunity, asserted action/change, first result/blocker, existing kind or unresolved status, bounded use, and loss.
direct relations	Related subjects, relation, source or evidence basis, truth status, and unresolved condition.
occurrence-evidence return, when current	The A.3.1.MR or ME.18 result with its own candidate statuses, real rivals, gaps and evidence limits. Include a distinguishing question only when it changes the receiving use, or a held-out result only when actually obtained. An ordinary account needs no prospective study to fill this row; raw observations are not documentary Method entries.
navigation	Open local sections used only for finding contributions.
downstream subjects	Identified Methods and individually scoped accounts with dependency slices for ME.5; a proposed-whole account with its identity/relation boundary for ME.7 when needed.
stop and return	Missing source, role, use, comparator, kind, relation, evidence, or the next receiving question.

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.

ME.4:4.3 - 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.

ME.4:5 - Archetypal Grounding — EC-417 Release Assurance Package

Source/use boundary for this constructed case: the EC-417 package snapshot specified below, used as documentary Method guidance for the changed release decision; recover the decision-bearing slice, and return when that package, receiving use, or a relied-on condition changes. This one sentence supplies the ordinary one-source contract.

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:

Local section	Recovered entries and statuses	Decision-bearing slice
Methods and candidate accounts	identified `M-HW-Verify`, `M-SW-Integrate`, `M-Supplier-Approve`, `M-Release-Authorize`; candidate `C-Evidence-Reconcile-Internal`, `C-Evidence-Reconcile-Supplier`, `C-AI-Trace-Review`, and proposed whole `C-EC-Release-v2`	Each Method or account keeps its source claims, required inputs/results, support, evidence, and limits.
descriptions, representations, and source claims	stage table, release checklist, supplier procedure, AI prompt, bundle records	These epistemes may describe or evidence a Method/account; none is promoted by its section.
Systems, support, and access	PLM, CI, test rig, AI provider, and provider-access condition	Availability and access are separate from Method identity and fit.
capabilities and assignments	safety competence, supplier-configuration responsibility, and release-authority assignment	Capability, responsibility, and authority are checked for the receiving use.
inputs, results, premises, and evidence	pinout schema, evidence bundle, verification result, confidentiality premise, and dated records	Each item keeps its direct kind and use.
relations	production/use, schema correspondence `A-17`, provider access, allocation, responsibility, and authority	Each relation is independently stated; no section or package edge supplies parthood.

Two example dependency slices show why the full package is neither copied nor discarded:

M-HW-Verify travels with its change input, verification-result meaning, rig condition, hardware capability, procedure provenance, and evidence window.
C-Evidence-Reconcile-Supplier travels with the supplier procedure, signed-evidence condition, supplier-configuration responsibility, closure authority, four observed source cases, and the unresolved A.3.1 identification 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; it does not silently occur inside ME.4.

The four identified Methods and the three individually scoped candidate accounts are potential ME.5 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 ME.7; its presence in the package creates neither a fifth Method nor methodPartOf facts.

ME.4:5.1 - 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, not external studies.

Source/use statement	Source-local contribution retained	Result and return
H/3 §4; maintained synthesis; full source-local within the supplier-evidence practice; return if that section or the receiving scope changes.	Missing supplier evidence can stop release. The source proposes reconciliation before authorization and names a signed-evidence result. It also names supplier access and authorization conditions.	Recover the reusable-way claim at its existing status with those conditions; preserve access and authority as different subjects. Return to H/3 §4 for its meaning.
C/2 §2; current comparator; SoTA-first for this decision; return if a rival or the comparison basis changes.	A separately reviewed evidence bundle is proposed to reduce reliance on one supplier account. Its first result is a reviewed bundle or a named evidence gap. The claim’s tested reach is limited to the comparison’s cases.	Retain this alternative and its limits separately from H. Do not decide that two differently supported activities are one Method or that either replaces the other.
I/D1; occurrence evidence, not a third documentary recovery profile.	The interview reports one release episode but does not yet distinguish a reusable way from a one-off response.	For the one-occurrence question use A.15.1. If several occurrences create a candidate-recovery question, use A.3.1.MR; keep a record-only lower result when that is all the evidence supports. ME.18 is not an automatic next step.

The first result is the two-source documentary dossier plus the honest occurrence-evidence return, not a merged release Method. A later semantic comparison must decide whether the two documentary contributions overlap, conflict, or complement one another.

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.

ME.4:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
source-taxonomy bias	Goal, procedure, rationale, framing, mindset, representation, role, or tool becomes a universal Method component kind.	Use those terms as source questions and place each returned claim with its actual subject.
diagram-containment bias	A box or lane is read as composition or parthood.	Require the direct relation and its evidence independently.
package-authority bias	Institutional or standards status becomes Method identity, fit, or effectiveness.	Separate source authority from the receiving claim and evidence.
procedure-only bias	A reusable action is extracted without rationale, applicability, input/result, support, or authority.	Carry the smallest dependency slice that can change qualification.

ME.4:7 - 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 ME.18; 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 ME.5 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.

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

Anti-pattern	Repair
Six local sections become six ontology kinds.	Call them open navigation and keep each entry’s existing kind.
Everything actionable becomes a Method candidate.	Require a reusable way-of-doing account; keep support, capability, evidence, and authority under their direct kinds.
The package is reduced to a procedure.	Recover rationale, framing, intended use, inputs/results, support, evidence, and authority only where they change the receiving decision.
The whole package is copied for provenance.	Attach a bounded dependency slice to each Method/account and retain a source return to the package edition.
Unknown relation is inferred from adjacency.	Record the relation as unresolved and state what observation or source would settle it.

ME.4:9 - 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. Some familiar package headings will disappear from the action path, while important support, authority, or evidence conditions may become more visible than the source’s headline procedure.

ME.4:10 - 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 deliberately 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.

ME.4:11 - SoTA-Echoing

Source	Retained contribution	Use boundary
Daalhuizen and Cash, Method Content Theory	Goal, procedure, rationale, framing, and mindset as questions that prevent procedure-only recovery.	Static content variables and initial study population do not define FPF kinds, Method parts, or cross-domain effectiveness.
Gericke, Eckert, and Stacey, Elements of a design method	Core idea, representation, procedure, intended use, tool, ecosystem, and adaptation prompts.	Source elements remain questions and source claims, not a universal dossier ontology.
Stacey et al., Methods as a form of engineering knowledge	Current comparison of engineering-Method knowledge and the placement of representations, framing, and rationale.	Conceptual comparison supplies no project Method identity or package parthood.
Current FPF `A.3.1`, `A.3.2`, `B.1.5`, and `F.18`	Method identity, MethodDescription membership, composition law, and name recovery.	The DPF adds the decision-bounded dossier and dependency-slice Method.

Reopen when a current source or package case exposes a decision-bearing contribution that cannot retain its kind, provenance, role, and relation in the open dossier; when a source profile hides material receiving conditions; or when the ordinary one-package result acquires burden that its use does not need.

ME.4:12 - Relations

A.3.1.MR governs candidate recovery from occurrence evidence; ME.18 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. ME.4 preserves the inputs and return paths but does not settle that next semantic question.
A.3.1 governs Method identity; A.3.2 governs MethodDescription claims; B.1.5 governs Method composition; F.18 governs durable name claims.
ME.1 supplies the focus and receiving decision when package recovery is the chosen next result. ME.2 may supply an inherited repertoire or source lineage.
ME.5 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.
ME.6 receives only a several-structure synthesis question that remains after individual qualification.
ME.7 receives a proposed whole account when its identity and relations must be resolved.