Construct and Qualify a Composite Method
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
Primary working result: a bounded composition result whose whole, participants, and load-bearing relations are independently supported; a prospective candidate Method account; or a useful narrower claim. Include the proposed relation sets, conditions and unresolved questions needed by the receiving use. Writing the account creates neither the Method nor an obtaining architecture.
Use this pattern when a proposal names an intended Method whole, such as a methodology or playbook, and the next decision depends on what is already established about that whole.
Relations
Content
Use This When
Use this pattern when a proposal names an intended Method whole, such as a methodology or playbook, and the next decision depends on what is already established about that whole.
Begin with the proposal's intended result, participants and relation claims. Recover the available whole semantics and the guards, burdens, unresolved conditions and selection reason that matter for the receiving use. Test the identity and relation grounds required for the conclusion sought.
The first useful result is two-branched. If the whole and participant Methods are identified and the required relations are shown to obtain, record the bounded composition result. Otherwise return the prospective account or partial claim supported by the evidence. That account can finish a present design comparison while whole identity or relation truth remains unresolved. Select later realization or testing only when its obtainable contribution warrants the full burden and is feasible.
Do not require prior performance of C.32.MWA.PP when equivalent proposal content is already available. Do not treat a coherent description, selected architecture, WorkPlan, tool implementation, or successful first trial as Method construction or identification by itself.
Working Distinctions
Problem Frame
Method Engineering often produces coherent proposals before the proposed practice exists. Situational Method Engineering and design-Method research offer useful construction and adaptation moves, while FPF keeps the proposed account, world-side Method, MethodDescription, WorkPlan, performed Work, and obtaining relations distinct.
A proposal can state an invariant, guards, variants, participant contributions, stops, and a bounded trial when one is selected. The error is reporting possible-future content as already obtaining.
Problem
One failure declares a whole whenever a document gives several steps a shared name. Another refuses to state anything useful until a mature Method has already been identified. A third treats participant co-use, Work order, or a successful tool integration as sufficient evidence for methodPartOf.
The first error overclaims, the second prevents learning, and the third confuses several relation structures. A prospective or partial account can support present comparison or later realization while keeping uncertainty explicit.
Forces
Solution
B.1.5 supplies the composition test. This construction supplies the candidate whole, constituent contributions, interfaces and grounds to which that test applies; it can also return a useful relation account below the whole-Method threshold. Use an already complete B.1.5 result directly rather than reconstructing it.
Recover the proposed whole's semantics, test whole and participant identity separately from relation truth, and return the branch supported by that evidence.
Pattern-Use Unfolding
- Name the receiving use. State the result or preserved condition, situation family, intended users or performers, and consuming decision. Identify the configuration or edition and time window when they change the claim or its use.
- Recover whole semantics. Recover the proposed whole's reusable operations or invariant, applicability, participant contributions, and the entry/exit, variation, bounds, stops and reidentification conditions needed for the claim. Keep proposed content, supported facts and unresolved grounds distinct. Missing content blocks only conclusions that require it; a supported prospective account or partial result may still complete the receiving use.
- Preserve participant statuses. Identify each Method under
A.3.1where supported. Keep candidate accounts and other subjects at their existing statuses. - Name the relation sets. State every load-bearing proposed or obtaining relation, including Method composition, Work order or overlap, result use, allocation, support/provider access, authority, and description correspondence as applicable. Do not infer one relation from another.
- Test the positive branch. Record an obtaining composition only when the whole and parts are identified as Methods and the required
B.1.5relations are shown to obtain within the bounded claim. - Return the prospective branch when needed. State the candidate whole, participant statuses, proposed relation sets, guards, adapters, alternatives, recovery, variation points, burdens and unresolved conditions needed for the receiving use. A traceable proposal can answer that use while its stronger whole claim remains unresolved.
- Return a supported partial result. When missing whole semantics, identity, or a relation prevents a useful candidate account, return the supported fragment, relation claim, WorkPlan question, or stop. Keep the missing grounds explicit.
- Choose a useful continuation when needed. Use C.11.DUA to compare the result a realizable implementation or trial could add with its full burden, including access, allocation, authority and the available window. When that Work is selected, name its observations, acceptance and failure conditions, any required authority, and the reconsideration rule; prepare a WorkPlan where coordination needs one. Otherwise finish with the supported account or partial result and the limitation that matters to its recipient.
Record the Result
What Changes in Practice
Practitioners can write and test a coherent proposed Method without pretending that documentation created it. A positive composition claim becomes stronger because its identity and relation evidence are explicit; a prospective account remains useful for comparison through its guards, variation, recovery and stated limits. A selected implementation or trial adds the continuation needed to learn more.
Archetypal Grounding — C-EC-Release-v2
The EC-417 project proposes C-EC-Release-v2 as a whole for safety-relevant release coordination.
Under A, the team waits for signed supplier evidence before integrating the software. Under B2, it integrates from a versioned provisional edition, reconciles it with signed evidence before safety closure, and assigns most preparation of the changes between the editions to the supplier-configuration role to keep the safety engineer within the peak limit. C.32.MWA.PP §5.3 gives the timing and capacity comparison. A can be selected only before integration; recovery R is used when closure fails after early B2 integration.
The proposed account states:
The four participant Methods are identified, but the proposed whole is not. Their co-use and the proposed order do not establish that they are Method parts. The relation sets therefore remain proposed:
- provisional-evidence integration at
D-21and signed-evidence reconciliation atD-8; - signed evidence and accepted safety result before release authorization;
- supplier preparation responsibility for
1.60 hunder B2; - separate safety and release authority;
- PLM, rig, and provider-access conditions; and
- description correspondences from evidence version through integration bundle and verification result.
For this selected trial, B.1.5.CM returns a prospective candidate account with a WorkPlan covering at most three B2 releases. The whole and relation claims remain proposed.
At each proposed release's D-21 entry checkpoint, SafetyReviewer-17 accepts or rejects the entry evidence under ASG-SafetyReview-17 and AUTH-SafetyEvidence-17; ReleaseDecider-17 then decides branch entry under ASG-ReleaseDecision-17 and AUTH-ReleaseDecision-17. The filled entry case identifies these decisions as W-SafetyEvidenceDecision-17 and W-ReleaseDecision-17.
For closure or recovery, the two decision-makers use the evidence then available to decide safety-evidence acceptance and release, withhold, or next-slot disposition under the applicable assignments and authorities. Each performed later or repeated decision is a distinct dated Work occurrence with its inputs and result. Neither decision or authority relation substitutes for the other.
In B2, TraceReviewer-17 accepts or rejects each AI trace suggestion used by the release branch under ASG-TraceReview-17 and PERM-TraceAcceptReject-17. The full EC-417 application, §16.9.5 records the one permission grant and the dated Work W-TraceAcceptReject-17-01 that returns acceptance in the filled case. The separate relation PEX-TraceAcceptReject-17-01 connects that dated Work to the permission it exercised. EV-PEX-TraceAcceptReject-17-01 supplies evidence about this exercise.
Each additional used suggestion requires its own dated decision Work and result, confirmation that the permission applies at that time, and its own Work-to-permission exercise relation.
If signed evidence is missing at the D-8 closure checkpoint, withhold release and enter recovery R. In R, preserve the performed-integration record and evidence history. Repeat the evidence comparison and affected verification when evidence arrives by D0 while the existing evidence and reversibility guards still hold. Record whether early integration is retained, rolled back, or repeated, and the added burden. If closure remains unresolved at D0, the release result is withhold/next-slot and this R occurrence ends as a failed B2 trial.
ASG-TraceReview-17 and PERM-TraceAcceptReject-17 end at D0; continuing safety or release relations extend neither. This trial provides no post-D0 AI-supported continuation and asserts no later Work or recovery WorkPlan. Unresolved R may motivate separate later planning.
When later non-AI recovery needs coordination, the project may create a new A.15.2 WorkPlan; A.15.2 does not require planning before every otherwise valid later Work. Planned or unplanned Work would still need its separate qualification/currentness, readiness, assignment, permission/authority, and A.15.1 occurrence as applicable. These stops preserve all earlier Work and evidence history. A is only a pre-entry alternative.
Acceptance observations include whether each trial respects confidentiality and authority, remains at or below the D-8 capacity bound, preserves evidence/version correspondence, and reaches a release or recovery result by D0. An attempted post-D0 AI-supported continuation, or an assertion of later Work without a separately admitted A.15.1 dated Work occurrence, is a stop and failed trial observation.
The withhold/next-slot result preserves earlier Work and may motivate later planning. Those observations may support, narrow, split, or reject the account. They do not by themselves identify the whole; A.3.1 remains the identity owner.
For this series, a release counts once as a failed trial if it has a capacity or supplier-pinout/integration-bundle mismatch failure or enters R, even if recovery later succeeds; keep all failure reasons.
After two distinct failed trials, ReleaseDecider-17, within AUTH-ReleaseDecision-17, returns B2 for revision or rejects further use. That disposition retains the separate safety decision and grants no authority to revise the account. The immediate confidentiality, assignment, permission and authority stops still apply to the first breach. The existing decision covers at most three trials; a further release needs a new applicable decision.
Finish a Design Comparison Before a Trial Is Available
Suppose an earlier design use asks whether this release-coordination proposal preserves signed-before-closure, confidentiality and the A/B2/R distinctions well enough to compare with another proposal. The sources support that account, but whole identity and composition relations remain unresolved, and the team has no rig access, allocated effort or trial window. Return the traceable prospective account with those identity and relation limits. The receiving designer can compare the proposals and finish that question on the available content.
A later opportunity with useful obtainable observations can warrant implementation or a trial and its coordination plan. The already selected three-release case above retains its WorkPlan, observations and stops.
Bias-Annotation
Conformance Checklist
- The returned claim states the whole semantics it needs: intended result or preserved condition, situation, reusable operations/invariant, applicability, participants and relevant variation, bounds and reidentification conditions. Missing grounds remain explicit in a prospective or partial result.
- Whole and participant identification are judged separately; candidate and unresolved statuses remain explicit.
- Method composition, Work order/overlap, result use, allocation, support, authority, and description relations are not inferred from one another.
- The positive branch requires identified whole and parts plus obtaining
B.1.5relations. - The prospective branch preserves proposed truth and includes the guards, adapters, alternatives, recovery, stops, burdens and unresolved conditions needed by the receiving use.
- WorkPlan, performed Work, observations, MethodDescription, and Method identity remain distinct.
- When load-bearing semantics or relations are missing, a supported fragment or relation claim can be returned without a complete candidate account.
- A supported account or partial result can complete its receiving use. Any selected continuation has a worthwhile feasible contribution and names the needed later Work, observations, any required authority, acceptance/failure and reconsideration.
Common Anti-Patterns and How to Avoid Them
Consequences
Projects can move from architecture proposal to realization and learning under identity and relation conditions. An established composition and a supported proposal remain distinguishable, and either can support the use for which its grounds are sufficient.
The cost is a visible open identity or relation question. Some proposed methodologies will remain candidate accounts after useful trials, and some will split into several Methods or a relation structure instead of maturing as one whole.
Rationale
Construction and description can change epistemes and WorkPlans immediately; they do not create a reusable way of doing in the world by assertion. The two-branch result preserves this difference while letting possible-future content guide real Work.
B.1.5.CM does not depend on applying C.32.MWA.PP first. C.32.MWA.PP is one common source of proposed relation sets, but any equivalent content can enter B.1.5.CM directly.
SoTA-Echoing
Reconsider the account when its content fits none of these supported results, when variation defeats its reidentification rule, or when the claimed composition depends only on Work order or co-use.
Relations
A.3.1governs whole and participant Method identification;B.1.5governs any Method-composition claim.- C.32.MWA.PP commonly supplies proposed relation sets and architecture alternatives, but it is not a compulsory predecessor.
- A.3.1.QM supplies individual qualifications without whole identity or compatibility.
- Later realization, identification, description, support, trial, and assurance patterns consume only the branch and truth status returned here.
- A prospective account, WorkPlan, selected architecture, or trial result supplies no obtaining ArchitectureRelation or
methodPartOffact by itself.
B.1.5.CM:End
Last Updated: 2026-11-03 — this section last modified in upstream FPF commit 4e2f3c97 (github.com/ailev/FPF)