Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:40:20 UTC

B.1.5 - Gamma_method - Order-Sensitive Method Composition and Work Enactment

Type: Part B composition and grounding pattern Status: Stable Normativity: Normative unless a section is marked informative

B.1.5:1 - Problem Frame

Use this pattern when a project must decide whether several recovered methods compose into one larger U.Method, and when order, guarded choice, parallel branches, typed joins, adapters, or method-interface exposure changes the identity of that whole method.

Typical moments:

  • a procedure, algorithm, or protocol has named steps or branches;
  • changing the order of two candidate submethods changes the result or the admissible conditions of use;
  • a diagram or code file looks like a method, but it may be only a method description, a work plan, a dated work trace, a selector registry, or a mathematical lens;
  • a larger method must expose some interactions at its boundary while hiding internal steps;
  • assurance needs to know which joins, adapters, cutsets, or exposed interfaces make the composite method reliable enough to enact.
  • a source presents Methods as a first–then list even though representative Work may also require several of them to contribute at the same time.

Primary EntityOfConcern. The EntityOfConcern is one candidate or composite U.Method, already identified under A.3.1. The proposition that part Methods and whole-forming facts qualify it as composite is separately governed claim content. A separately identified C.2.1 episteme may carry that proposition in its ClaimGraph; the episteme then has the candidate Method as its EntityOfConcern under its effective ReferenceScheme.

First useful move. For each apparent step or branch, recover the governed object before composing anything: U.Method, U.MethodDescription, U.WorkPlan, dated U.Work, an A.22-selected U.Structure, method-family registry or selector outcome, mathematical lens, mechanism, formal substrate, or quoted wording that does not yet carry a method claim.

What goes wrong if missed. A flowchart becomes the method, a plan item becomes a submethod, an event log becomes proof that a method was enacted, an order edge becomes a part, or a registry of alternatives is treated as one composed method. Then work starts from a description or label whose method identity, joins, interfaces, and failure conditions were never recovered.

What this buys. The project can test whether an already identified candidate U.Method is composite and state the part, order, join, interface, and identity facts needed for that claim. If qualification fails, another useful result may remain, such as a description, plan, selected structure, or selector result, under its pattern. Use A.15.4 when the failed qualification reveals reliance on appearance.

Not this pattern when.

  • If the claim is one semantic way of doing with no order-sensitive composition question, use A.3.1.
  • If the claim is a claim-bearing episteme that describes a method or relations among methods, use A.3.2 and C.2.1.
  • If the claim is intended work, use A.15.2.
  • If the claim is a dated occurrence, use A.15.1.
  • If the claim is structural component parthood, use A.14; use C.13 for a needed construction account and B.3.5 only when its additional assurance profile is elected.
  • If the claim is only a method-family registry, selector, fallback relation, or useful organization of already identified methods without one whole-method construction, use G.5 or select a U.Structure under A.22.

B.1.5:1.1 - Composition Question And Object Boundaries

U.Method is a non-agentive method holon kind. A method can have submethods and can participate as a submethod in a larger method. This does not mean every step-looking node, document section, file module, graph edge, work-plan item, or work occurrence is a method part.

Order-sensitive method composition asks:

Given independently recovered U.Method parts,
which methodPartOf occurrences, whole-forming claims, and constraints qualify one already identified candidate as composite,
and what whole-level commitments let a practitioner identify, reidentify, and enact that method?

The whole method is not the diagram, code, schedule, event log, card, or work history that may describe, plan, record, or evidence it. Work enacts the method; the method does not perform work. An A.22-selected U.Structure may organize several methods and obtaining relations for one use without constructing another method.

Gamma_method names this method-composition discipline. Use the patterns above for related objects and B.1.6 for resource accounting.

B.1.5:2 - Problem

When the objects and composition grounds are left unclear:

  1. Source-wording composition. A label such as “step”, “workflow”, or “algorithm” is accepted as method composition without recovering the objects.
  2. Description-as-method. A workflow diagram, BPMN model, code repository, proof script, table, checklist, or graph path is treated as the composite method.
  3. Order as mereology. SerialStepOf, ParallelFactorOf, guarded choice, or fallback relation is placed in a structural part-whole chain.
  4. Typed joins disappear. One submethod’s intended result is assumed to satisfy the next submethod’s precondition without checking their compatibility, any needed adapter Method or governed correspondence, and the failure route.
  5. Interface exposure is hidden. Callers rely on internal interactions that should be encapsulated, or fail to see interactions that the composite method must expose.
  6. Run-time leakage. Resources, timestamps, telemetry, performed values, and results are baked into the method instead of remaining occurrence-side facts and separately governed resource, result, and evidence relations.
  7. False whole method. A method-family registry, fallback table, selector rule, or A.22-selected relation organization is treated as one whole method although no construction or whole identity has been recovered.
  8. Sequence becomes level. A source list, vertical diagram, curriculum, or first–then account is treated as a subject hierarchy or level structure without an independently established level relation.
  9. Simultaneous contributions become stages. Methods that contribute during the same bounded Work situation are forced into one before-after chain because the source, presentation, or review visits them one at a time.

B.1.5:3 - Forces

ForceTension
Method reuse vs source examplesTeams need a reusable way of doing, while sources often show only one description, run, or plan.
Order fidelity vs compact modelingImportant sequences and joins must remain explicit without turning every diagram edge into ontology.
Order vs simultaneous contributionA first–then condition must survive, while Methods that contribute together must not be invented as stages merely because they are described in sequence.
Whole-method identity vs relation usefulnessSome method-side relations are useful without asserting one composite method whole.
Interface exposure vs encapsulationA composite method must state which interactions callers may rely on and which remain internal.
Assurance vs executionAssurance needs joins, adapters, cutsets, and failure conditions; dated enactment, result, and evidence-use claims stay with their subject patterns.

B.1.5:4 - Solution

A.3.1 first identifies the candidate U.Method and every part method. B.1.5 does not create their U.Method membership. It asks: do these already identified methods, contributions, constraints, and boundary decisions warrant the claim that the candidate Method is composite?

Start with the smallest useful composition claim:

  1. Name the same A.3.1 candidate Method and A.3.1 part methods.
  2. In ordinary domain language, state the candidate’s reusable whole action, what each part contributes, and the order, guard, adapter, or join condition that the whole action needs.
  3. For every whole-forming statement other than B.1.5’s methodPartOf, use A.6.RCD’s lightest sufficient disposition: an existing direct predicate, a local compound claim, or a reusable predicate-definition episteme. A convenient edge label is not a relation-kind admission.
  4. Add stable relation-occurrence identity, typed declarations, publication, or assurance only when a named dependent use consumes that extra result. Submit any relation-kind candidate to the E.24/E.24.UK admission predicates rather than admitting it here.
  5. If the whole action, boundary, contribution, or reidentification rule is still missing, stop the composite claim. Retain any independently supported description, plan, structure, or other result under its subject pattern.

Minimal positive. BuildAndVerifyPumpUnit is already an A.3.1 Method. Its construction rule requires frame assembly, motor installation, connector adaptation when the installed connector does not meet the test precondition, and functional testing; installation and any required adaptation must finish before testing, and adapter failure stops the whole before test. These plain claims, methodPartOf facts, and the whole identity rule can warrant the composite-method qualification without minting one relation kind per arrow.

Discriminating non-composite. AssessVitals, ClassifyUrgency, and RouteToCare can support result-to-precondition and guarded-dispatch claims while still lacking one reusable whole action, complete boundary, and whole reidentification rule. Keep those claims local and do not call their organization a composite Method. Select an A.22 U.Structure only if a receiving use needs a selected organization.

When a receiving use relies on the composition account—for example, planning, Method substitution, or assurance—check the questions below. They guide reading; they do not declare a schema or relation signature.

Composite-method qualification:
  candidate whole method: one U.Method already identified under A.3.1
  part methods: a non-empty set of U.Method values already identified under A.3.1
  method-part occurrences defined in B.1.5: methodPartOf(part method, whole method)
  other whole-forming claims and constraints:
    order, independence, guard, iteration, fallback, adapter, and join meanings used here
    each closed at A.6.RCD's lightest sufficient disposition
  whole semantics:
    generic participants, applicability, preconditions,
    intended effects or preserved conditions, invariants, bounds,
    accepted inputs and outputs, failure and stop conditions
  boundary decisions:
    exposed, forwarded, and encapsulated interactions
  identity and reidentification:
    what keeps this whole the same and what identifies another method
  enactment boundary:
    U.Work may enact the method only through A.15.1 enactsMethod
  other independently supported results if composition is incomplete:
    for example, a description, plan, selected structure, selector result, or Work claim
    use A.15.4 when reliance on appearance needs repair

B.1.5:4.1 - Recover Parts Before Composition

Do not start from the word “step”. Start from the object claim.

An apparent step can be:

  • a U.Method submethod;
  • a description constituent inside U.MethodDescription;
  • a plan item inside U.WorkPlan;
  • a dated U.Work occurrence or work part;
  • an order, fallback, or selector claim among independently identified objects;
  • a mathematical or representation lens over selected relations;
  • mechanism or formal-substrate material;
  • quoted wording that does not yet carry a method claim.

Only an independently identified U.Method can be a method part; keep the other objects under their patterns.

B.1.5 governs MethodPartOfRelation, expressed in Plain register as methodPartOf(partMethod, wholeMethod). Both participants are U.Method values already identified under A.3.1. The predicate obtains exactly when the whole Method’s stable construction rule names the part Method as a required contributor or as an admitted alternative for a required contribution, and that contribution participates in the whole’s reusable action. It establishes neither A.14 structural-component parthood, a work part, nor a transformation part.

One methodPartOf occurrence is determined by the ordered pair <part Method, whole Method>. Every bounded alternative already admitted by the whole’s construction rule can stand in methodPartOf at the same time; dated Work selecting one alternative does not start, end, or recur the other occurrences. For the same two Methods, the relation is atemporal: there is no cessation and later recurrence.

If the construction rule changes so that a part is newly admitted or no longer admitted, the composite Method must be reidentified or the claim remains unresolved; reidentifying either participant gives another pair. This is why the participant pair is sufficient for the family defined in B.1.5 even when enactments vary.

The same part Method may also stand in methodPartOf relations to several whole Methods. Test every pair against the construction rule of its whole. Each whole keeps its reusable action, applicability, boundary, constraints, interfaces, accepted variations, and reidentification rule. One supported pair says nothing about another and creates no unique containing Method, discipline-wide whole, kind inheritance, transitivity, fusion, or common-whole closure.

A source label, list membership, diagram containment, shared name, registry entry, description membership, plan position, or work decomposition does not make methodPartOf obtain. When the test fails, keep the apparent step under its subject pattern and do not add a negative part merely to complete a diagram.

B.1.5:4.2 - Test The Composite-Method Qualification

First identify the candidate Method under A.3.1 from its reusable action, participant meanings, applicability, preconditions, intended result or preserved condition, bounds, and failure or stop conditions. If that Method cannot yet be identified, require A.3.1. B.1.5 then tests whether already identified part Methods and whole-forming facts justify calling that same candidate a composite Method; it does not create the candidate’s Method identity.

State each whole-forming fact in ordinary domain language before choosing its representational or ontological disposition. The words serial, parallel, guarded, iterative, fallback, adapter, and join do not settle the claim by themselves.

Composition cueWhat the claim must let a practitioner decide
serialwhich earlier and later Methods participate in which whole, and which accepted result or preserved condition of the earlier Method must satisfy which precondition of the later Method before continuation
parallelwhich branch Methods may proceed without a mutual order, the independence condition, and the join condition that must hold before the whole continues
guarded choicewhich alternative Method is selected, the selection condition, what happens when no guard or several guards hold, and which whole contains that choice
iterationwhich part Method repeats, what establishes another iteration, and the stop or failure condition
Method refinement or substitutionwhich Method may replace which other Method, for which use, and which whole semantics, joins, and exposed interactions must remain invariant
fallback or dispatchwhich primary and alternative Methods are involved, the trigger for using the alternative, and whether the statement belongs to this whole or only to a selector registry
adapter or typed joinwhich upstream result meaning satisfies which downstream precondition, which adapter Method or governed correspondence is needed when those meanings differ, and which condition or failure route governs continuation

Use B.5.MR for refinement or abstraction between models of Methods. Establish a comparison between the Methods themselves through A.3.1’s identity and relation conditions. The model comparison alone replaces no constituent Method.

Before using a first–then or vertical list as Method architecture, make both checks.

  1. Preserve order. Ask what must finish or become true before another Method can start or continue. Name the Methods, the required result or condition, any join or adapter, and the failure or stop route. Keep a first–then result as an unfolding or order claim; its position does not make it a subject level.
  2. Test simultaneous contribution. Choose a representative working situation and ask whether several Methods contribute without forming one before-after chain. They may be enacted in one Work whole or in overlapping Work occurrences. When asserting dated occurrences, identify those Work individuals and their obtaining A.15.1 enactment relations. Co-occurrence alone establishes no Method part, composite Method, Work part, or level.

Both answers may be true. A Method can contain an ordered segment while other Methods contribute during the same broader Work. The source’s reading order and the fact that several Methods are used together decide neither which Methods are parts of one whole nor whether any level exists.

Then use A.6.RCD. Reuse an existing direct predicate when one already governs the needed claim. Otherwise stop at a local compound claim when it closes this use, or publish a reusable predicate-definition episteme when several uses need the same rule. Continue to a relation-kind candidate only when a named receiver needs stable occurrence semantics that claim content cannot supply; E.24 and E.24.UK decide admission. A label such as precedesInMethod is claim language, not admission evidence, and an ordinary composition claim needs no invented occurrence.

Keep definition, signature, kind, and edition distinct. A predicate-definition episteme may independently satisfy ordinary A.6.0 U.Signature membership. It is not a RelationSignature; that specialization opens only for an admitted relation kind.

Changed predicate-definition or signature content identifies another episteme under C.2.1. Treat and connect the two epistemes as editions through EpistemeEditionRelation only when C.2.1’s historical-continuation test passes: source use and the continuation rule identify which claim, EntityOfConcern, and scheme features must be preserved or may deliberately change, and the facts satisfy that rule. Revision or supersession Work, Method, provenance, and change facts are evidence for this test; no label establishes continuity. Otherwise the later episteme is a non-continuing replacement.

The changed content triggers review of dependent claims; it does not by itself prove another relation kind or relation occurrence. If a relation kind is independently admitted, its pattern or declaration defines applicability and occurrence identity, while case facts establish obtaining, continuation, or cessation where relevant.

When the receiving use needs to combine order information, apply B.1.4 to the selected inputs, combining rule, and required order, join or independence conditions. State the OrderSpec, the required ordering over the identified positions, in adequate prose or the representation consumed by the receiver; identify each claimed relation occurrence under its predicate.

An adequate explanation or existing account may suffice. Materialize a separate aggregation record only when the receiver needs it. The account and optional notation describe the composition facts; they add no Method identity discriminator and make no relation obtain.

The composite-method qualification holds only when the candidate Method also has its reusable semantic action, generic participant meanings, applicability, preconditions, intended effects or preserved conditions, invariants, bounds, accepted inputs and outputs, failure and stop conditions, and interface decisions. Its identity includes the part Methods and construction architecture on which those semantics depend.

Cite an effective reference scheme or claim scope only when its variation changes a Method meaning or the use of a claim about that Method; neither is a generic container.

State the reidentification rule with the qualification. The same candidate continues through only those parameter changes, reorderings, or part substitutions that its A.3.1 identity rule already permits while preserving the whole action, applicability, preconditions, intended result or preserved condition, bounds, required joins, and interface boundary. A change outside those permitted variations identifies another U.Method. Use B.2 when a separate higher-level reidentification or emergence claim is current; a B.2 label is not needed to state a B.1.5 rule.

B.1.5:4.3 - Keep Order Out Of Structural Mereology

Source cues such as SerialStepOf, ParallelFactorOf, guarded choice, iteration, fallback, adapter, and typed join call attention to possible whole-forming claims. They are not admission evidence, they need not become relation kinds, they are not A.14 component parthood, and they do not make methodPartOf obtain by themselves.

Use A.14 for structural parts of a holon, C.13 for their construction account when needed, and B.3.5 when the additional assurance profile is elected. Use B.1.5 for the contribution of reusable ways of doing to a larger reusable way. A project may need both claims; each retains its participants and truth conditions.

B.1.4 can supply an order aggregation, partial-order test, or join/independence account. Recover the selected inputs and combining rule, including the required ordering specified by OrderSpec; B.1.5 still decides whether the Methods and their construction facts constitute one composite U.Method.

When the claim is a proper temporal restriction of one unchanged non-Work carrier, apply that subject’s identity rule and A.14/B.1.4 rather than B.1.5. For MethodDescription history, compare the C.2.1 identity triples and assert EpistemeEditionRelation only when its historical-continuation predicate obtains.

For Work intervals, episodes, performed parts, retries, resumptions, or later occurrences, apply A.15.1’s relations; generic PhaseOf is not their substitute. A temporal boundary becomes a B.2-family question only when a separate whole-reidentification, closure, or supervision claim remains.

Order, temporal restriction, episteme edition, Work segmentation, structural parthood, method composition, and whole reidentification remain different claims even when one source diagram uses one line for all of them.

B.1.5:4.4 - Expose The Composite Method Interface

The candidate Method’s reusable action includes a boundary decision for each interaction:

  • exposed: a caller system may rely on the interaction as part of the whole Method;
  • forwarded: a caller system may address an internal submethod interaction through a declared designation or adapter;
  • encapsulated: the interaction is internal and cannot be relied on from outside the whole Method.

An exposure decision contributes to Method identity whenever changing it changes the reusable action or its admissible boundary. That identity consequence does not wait for an outside party to rely on the Method.

A named caller, planner, auditor, substituting-method selection use, or assurance use instead determines when the decision must be stated or published for reuse. Name the interaction, precondition, result or preserved condition, failure route, and any adapter needed for each exposed or forwarded case.

B.1.5:4.4.1 - Composite-Method Boundary Account and Publication Form

State the boundary decisions in sentences: what a caller may request, what it must supply, what result or preserved condition it may rely on, and what stops the interaction. Name any needed adapter, order condition, bound, or assurance limit. Explain an encapsulated interaction when a plausible caller could otherwise rely on it. This can complete an internal boundary account.

When a receiver needs the published account, say which MethodDescription edition is available, to which declared audience, for which bounded use, through which expression and carrier. A.3.2 and C.2.1 identify the description; E.24.PUB supplies the publication relations and their progressive explicitness. Name a reusable boundary-account form only when its arrangement rules matter. The form, its conforming expression and the carrier retain separate identities.

For disputed availability or publication identity, recover E.24.PUB’s five participants <description edition, audience declaration, bounded-use declaration, expression, carrier>, its supporting expression and bearing relations, and the maximal continuous availability interval. If form conformance is used, the same expression must support the form-mediated claims. Publication activity is separate; identify dated publication Work only when that occurrence is asserted. Names and links retain their designation meaning.

Optional prompts for the receiving account:

  • the described Method and the description edition used;
  • exposed and forwarded interactions, accepted input meanings, preconditions, intended results or preserved conditions;
  • required invariants, failure routes and stops;
  • order or join conditions, adapters and applicable bounds that affect the receiver’s use;
  • the audience and bounded use when the account is published.

Use an existing adequate account without adding a form. These presentation prompts supply no Method parts or composition facts.

B.1.5:4.5 - Keep Method Qualification And Work Occurrence Separate

B.1.5 evaluates and grounds the composite-method qualification of a U.Method already identified under A.3.1. A separately constituted U.MethodDescription may state that composition claim. Neither object creates performed Work.

One dated U.Work occurrence enacts one U.Method only when the A.15.1 method-enactment relation obtains. Recover each performer through A.13; A.15.1 then independently identifies the Work, time, containing System, and enacted Method.

F.6 enters only when the Method-enactment account also consumes assignment-bound attribution through the same obtaining A.13 assignment; missing or failed F.6 alone leaves independently grounded Work and enactment intact. If the same finding invalidates a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent conclusions while preserving independently grounded history and relations.

The performing System acts under the recovered relations. An assertion or occurrence description may cite those facts and the MethodDescription used.

Parameter bindings, affected referents, resource use, telemetry, retries, results, transformations, production, evidence, evaluation, delivery, and acceptance remain separate objects and relations under their governors. They do not become method parts, method identity fields, or generic Work outcomes merely because a report places them beside the Work.

The composition link is not one-to-one. A Work occurrence may enact the whole method without exposing every submethod as a separate work part. An A.15.1 TemporalPartOf_work may enact the same whole method during its selected interval. An A.15.1 episode may span several method factors, repeat one factor, or be split by evidence policy without changing the method identity.

Conversely, a work part does not establish a submethod. A work part enacts a submethod only when that submethod is already an independently identified U.Method and a separate enactsMethod(workPart, submethod) occurrence obtains.

Reader check. Before saying that a work part enacts a submethod, name both sides:

  • the occurrence-side object: parent U.Work, obtaining work-part relation, interval or boundary, and performer System recovered through A.13; only when this reader check consumes assignment-bound attribution, also name the covering A.2.1 assignment and obtaining F.6 relation; add any separately obtaining resource or evidence relation only when used;
  • the method-side object: A.3.1 submethod, methodPartOf occurrence, whole-forming claim at its A.6.RCD disposition, preconditions, intended result or preserved condition, interface boundary, and whole-Method identity;
  • the cross-side fact: the enactsMethod(workPart, submethod) occurrence.

If one of these grounds is missing, leave that claim unresolved while retaining the independently supported claims. A Work part and a submethod each need their grounds. Keep a method-description node, evidence segment, mechanism material, system-component behavior, or A.15.4 appearance-based reliance repair request under its subject pattern.

For a working question—what larger work is being done through this action now—use B.1.5.EW. It recovers the constitutive connections at the needed grain and shows how a changed encompassing condition changes the action. An ongoing whole need not be completed, and its constituents need not all act at once. When changing a constituent for use in one or several wholes, B.1.5.RS follows the change through their entry conditions, interactions and required results. The qualifications above still decide the corresponding Method and Work claims.

B.1.5:4.5.1 - Planning And Performed-Work Obligations

B.1.5 has three common use positions, but they are positions in use, not U-kinds:

  • Planning or description-side use. To plan enactment, recover the Methods, methodPartOf facts, other whole-forming claims at their A.6.RCD dispositions, needed order and joins, interface boundary, invariants, and whole-level commitments. A resulting U.WorkPlan uses A.15.2 and may cite the MethodDescription edition on which it relies. Identify dated planning Work under A.13 and A.15.1 only when that occurrence is asserted; planning and its product remain separate from Method identity.

  • Performed-work use. Recover each performer through A.13, let A.15.1 independently admit the Work, and recover the enactsMethod occurrence for the whole Work. Add the covering A.2.1 assignment and F.6 relation only when this use consumes assignment-bound attribution; missing or failed F.6 alone leaves independently grounded Work and enactment intact. If the same finding invalidates a premise consumed by A.13 or A.15.1 admission, recheck that premise and its dependent conclusions while preserving independently grounded history and relations.

    Check capability fit or admission only when the work-entry decision consumes those claims; then check preconditions, order conformance, and exposed or forwarded interactions through their subject patterns. State resource use, evidence, and results only through their obtaining relations. None becomes part of the method.

  • Assurance use. Identify cutset submethods, fragile typed joins, adapter points, mapping congruence or CL-sensitive edges, and the envelope or scope in which the composite method is expected to hold. B.3 and related assurance patterns evaluate those hooks; B.1.5 only makes them visible.

Useful invariants remain:

  • A single recovered submethod composed alone does not create a surprising new Method.
  • Order is deterministic only under the order claims and conditions at their selected A.6.RCD dispositions.
  • Any throughput or quality bound must name its characteristic, critical path, and weakest-link basis.
  • A claim that improving a submethod, adapter, or typed join improves the composite must name the characteristic and conditions under which that improvement transfers.
B.1.5:4.5.2 - Stop Before Transformation Composition

Method composition and Work decomposition establish no U.Transformation part, composite transformation, transformation atomism, or TransformationPartOfRelation. Even when several method parts address the same referent and one Work enacts the whole method, identify each transformation independently under A.3.4. If a claim needs transformation composition and no transformation-composition governor supplies its participants, obtaining rule, and occurrence identity, return missing-governor[transformation-composition] for the proposed whole and independently identified changes. Do not infer either composition or indivisibility from the gap.

B.1.5:4.6 - Select A Structure Below The Whole-Method Threshold

When the organization itself answers a needed question, use A.22 to select a U.Structure over independently identified Methods and obtaining relations. State its four identity discriminators: constituents, selected relation occurrences, applied constraints, and use frame. Ordinary prose or an existing adequate description can supply them.

An asserted dated selection Work needs its A.13/A.15.1 grounds; add an operation binding or result episteme when the receiving claim needs one. A local comparison can also suffice without selecting a structure. MethodRelationStructure is a local designator for a selected structure, not a new U-kind.

Typical cases:

  • a fallback registry selects among alternatives but supplies no whole method;
  • a workflow diagram relates method descriptions but does not recover method parts;
  • a method family has independently governed refinement, substitution, or dispatch relations;
  • a graph or algebra represents selected method relations as a lens;
  • the same method labels occur under different effective reference schemes, while the local senses have not been resolved and any F.9 Bridge would establish only sense correspondence, not method identity;
  • a work plan orders tasks but does not define one reusable method.

The selected structure is a dependent organization for its named use. It does not create its constituents or relations, become a Method, or supply holonhood. Conversely, the internal construction of one Method whose composite qualification has been established does not become a second generic structure merely because a diagram can display it. Select a U.Structure only when that organization itself changes the next question or action.

A selected structure is useful when the question concerns relation organization and does not require a composite Method.

B.1.5:5 - Archetypal Grounding — Worked Slices

B.1.5:5.1 - Manufacturing Recipe

AssembleFrame, InstallMotor, AdaptMotorConnector, RunFunctionalTest, and BuildAndVerifyPumpUnit are U.Method values already identified under A.3.1; the last is now the candidate for a composite-method qualification. The four participant-determined occurrences methodPartOf(AssembleFrame, BuildAndVerifyPumpUnit), methodPartOf(InstallMotor, BuildAndVerifyPumpUnit), methodPartOf(AdaptMotorConnector, BuildAndVerifyPumpUnit), and methodPartOf(RunFunctionalTest, BuildAndVerifyPumpUnit) obtain because the stable whole construction rule names each contribution.

Every already admitted connector-adapter alternative may stand in methodPartOf simultaneously; one Work occurrence selecting an alternative does not toggle those atemporal occurrences. Removing a contribution from the construction rule, adding a new admitted alternative, or changing a required order, join, whole result, or boundary outside the declared variations identifies another whole Method.

For this use, say: the installed motor must provide the harness-installed condition required by functional test; when the supplier connector does not provide it, AdaptMotorConnector must provide the conversion before test; adapter failure stops the whole before test.

In this one use, PumpInstallBeforeTest and PumpConnectorAdapterJoin are labels for local compound claim content in the PumpBuildCompositionDescription-v1 : U.MethodDescription episteme under A.3.2 and C.2.1, not relation-kind names or occurrence designators.

If several pump-family uses need the same parameterized rule, A.6.RCD can identify a reusable predicate-definition episteme. Only a later named receiver that needs stable occurrences can justify evaluating a derived-kind candidate under E.24 and E.24.UK.

The composite qualification additionally requires the candidate’s generic participants, applicability, preconditions, accepted inputs, final effect, preserved conditions, exposed start and abort interactions, encapsulated calibration interaction, failure routes, and reidentification rule. A list of the five names or an arrow diagram establishes none of these facts.

PumpUnitBuildWork-2026-07-29 may enact the whole through one enactsMethod occurrence without four corresponding work parts. If a separately admitted MotorInstallationWorkPart-2026-07-29 exists, it enacts InstallMotor only through its enactsMethod occurrence. Resource use, test telemetry, the produced pump unit, acceptance, and evidence remain under their subject patterns.

B.1.5:5.2 - Emergency Intake

RegisterPatient, AssessVitals, ClassifyUrgency, and RouteToCare are independently identified Methods. For a one-off protocol review, the practitioner may state two local claims in ordinary language: the intended vital-sign result meaning of AssessVitals must satisfy the admitted input meaning of ClassifyUrgency; and the declared triage rule decides which admitted urgency category holds from the declared vital-sign conditions and, when the protocol uses them, the declared symptom conditions, then maps that category to one compatible RouteToCare.

If no category or several incompatible categories hold, the practitioner stops the routing decision and returns the guard rule for repair. These are useful claim contents, not MethodResultPreconditionRelation or MethodDispatchRelation admissions.

The two claims can finish this protocol comparison. If the receiving question instead needs a selected U.Structure, recover all four A.22 discriminators: constituents, independently obtaining relation occurrences, applied constraints, and use frame. The local claims cannot be relabelled as relation occurrences. Identify dated selection Work only when that occurrence is asserted, and a separate result episteme when the judgment must persist.

The comparison still discriminates the non-composite case. No reusable whole action, complete precondition-to-result boundary, response to every guard conflict, or whole reidentification rule has been established.

A wall poster may be a carrier bearing an expression that conforms to a publication form. A U.MethodDescription edition is the claim-bearing episteme conveyed by the expression; a publication occurrence makes that edition available to an audience for a bounded use.

For intake Work, recover each performer through A.13 and admit the Work independently through A.15.1. Only if this comparison also consumes which assignment covered that Work should it separately check the A.2.1 occurrence and obtaining F.6 attribution; capability or admission claims consumed by entry remain separate. None of these facts is a Method part.

If a later hospital protocol first identifies an A.3.1 Method such as EmergencyIntakeMethod-v4 with the missing whole semantics, B.1.5 can test its composite-method qualification. Neither a poster, the one-off comparison, nor a later selected structure turns into that Method.

B.1.5:5.3 - Learned Model Pipeline

A neural-network pipeline may describe feature extraction, embedding, attention, retrieval, ranking, and explanation generation. Some blocks may be formal substrate or mechanism material, some may be constituents of a U.MethodDescription, and some may be recovered as U.Method values.

After the candidate whole represented by the pipeline and every claimed part have been independently identified as A.3.1 Methods, that candidate qualifies as composite only when methodPartOf occurrences, whole-forming claims at their A.6.RCD dispositions, accepted inputs and outputs, invariants or admissibility conditions, typed joins, fallback behavior, failure conditions, interface decisions, and reidentification rule are present. Otherwise keep the graph as a MethodDescription, mathematical lens, mechanism material, or—when a selection basis and receiving use exist—an A.22-selected U.Structure.

Suppose one dated training Work enacts the pipeline Method while three independently identified transformations occur: the feature store changes, model parameters change, and the ranking index changes. Common Work, shared data, Method order, and temporal adjacency do not establish transformation parts or one composite transformation.

Without a transformation-composition governor, retain the three transformations and return missing-governor[transformation-composition] for the proposed three-change whole; do not call them atomic either.

B.1.5:5.4 - Evidence Synthesis And Publication

CollectDatasets, NormalizeSchemas, EstimateModel, CrossValidate, DraftManuscript, and EvidenceSynthesisAndPublication-v3 must first be A.3.1 Methods. B.1.5 can qualify the last as composite only when every claimed methodPartOf occurrence obtains and its whole-forming claims and constraints pass A.6.RCD’s lightest sufficient disposition.

In ordinary language, the intended result of NormalizeSchemas must satisfy the admitted input meaning of EstimateModel; legacy datasets may require adapter Methods; CrossValidate may be a critical cutset for later assurance; and a provenance condition may be a precondition of DraftManuscript before publication Work begins.

A paper draft, workflow diagram, repository, or notebook may be a claim-bearing episteme, a representation, or a carrier; its form does not make it the Method. Publication Work is U.Work. Compute, storage, reviewer time, artifact production, release, and acceptance stay with their subject patterns.

EvidenceSynthesisInterfaceDescription-v3 : U.MethodDescription states that the Method exposes Submit() and ReleaseArtifacts(), forwards CrossValidate.Folds(k), and encapsulates ad hoc scrubbing utilities. A submitting researcher can use this boundary account to distinguish supported calls from internal operations.

For the published account, EvidenceSynthesisMethodsPage-2026-07 is the digital carrier of an ordered-text expression of that edition. SubmittingResearchersAudienceDeclaration-v1 identifies the authorized submitting researchers; SubmissionAndArtifactReleaseUse states the supported submission and artifact-release operations, their conditions and any needed stronger-use boundary. If the selected SubmissionReleaseBoundaryAccountForm-v3 constrains the arrangement, check that this expression conforms to it.

E.24.PUB tests whether the same expression conveys the required claims, is recoverable from that carrier, and is available to the declared audience for that use. Its five participants and maximal continuous availability interval identify the publication occurrence. Uploading or granting access may establish that availability; an assertion of publication Work has separate A.13/A.15.1 grounds. Availability alone establishes neither actual use nor the Method’s composition facts.

B.1.5:5.5 - Ordered Preparation And Simultaneous Performance

A music-and-dance performance can contain both kinds of fact. Venue setup, safety checks, and interface checks may need an order before the public performance starts; a failed safety check may stop the unfolding. Preserve that order when the Methods and conditions support it. It is not a level structure.

During the performance, dancing, music making, sound mixing, lighting, and stage coordination may contribute at the same time. If the project identifies one performance Work whole, it may enact several Methods through separate relations. If it identifies several Work occurrences, state which overlap. Do not rewrite these contributions as five stages merely because a production plan or review lists them one by one. Conversely, do not erase setup, cue, or handoff order merely because the overall performance is simultaneous.

The same two-way check applies elsewhere. In engineering Work, a lifecycle or product order does not prove that architecture, realization, integration, assurance, and feedback form one sequence. In operating Work, a workflow line does not serialize queues, commitments, resources, measures, and improvement. In capability development, preparation Work may precede the target Work while several target Methods contribute together during the transfer check. Preserve every continuation condition, but do not invent order among concurrent contributions.

B.1.5:6 - Bias-Annotation

The following risks concern cross-domain order-sensitive composition of already identified U.Method values. B.1.5 does not cover sole-Method identification, description-only organization, dated Work decomposition, structural mereology, or transformation composition without a governor.

  • Gov: each methodPartOf occurrence and each other whole-forming claim stays with its governor; a named receiver changes how much of the boundary account must be stated or published, not whether a world-side fact obtains.
  • Arch: the whole is qualified from part Methods and construction facts; order aggregation, a selected A.22 Structure, and a separate higher-level reidentification claim remain distinct architectural objects.
  • Onto/Epist: Methods and obtaining relation occurrences remain distinct from MethodDescription claims, boundary-account presentation, carriers, publication Work, and publication occurrences.
  • Prag: ordinary use may stop at local claims; reusable definitions, relation kinds, declarations, publication, and assurance are added only when a named receiving use needs them.
  • Did: the manufacturing, emergency-intake, learned-pipeline, evidence-synthesis, and performance slices show positive composition, useful non-composite stopping results, and the difference between order and simultaneous contribution across domains.

Construction and boundary accounts are useful when a join or outside reliance depends on them. Keep a local claim when it supplies the needed result, and use another pattern for a different object or relation.

B.1.5:7 - Conformance Checklist

CheckRequirement
CC-B1.5-1The candidate whole and every claimed Method part are independently identified as U.Method values under A.3.1 before B.1.5 tests the composite-method qualification.
CC-B1.5-2Step wording, description nodes, plan items, Work occurrences, file modules, graph edges, registries, source wording, mechanism material, formal substrates, mathematical lenses, and evidence or publication-use claims are not Method parts by position or label. Keep each with its governor unless it is independently identified as a U.Method and methodPartOf separately obtains.
CC-B1.5-3Every methodPartOf(partMethod, wholeMethod) occurrence passes the required-contribution or admitted-alternative test. Its identity is determined by the ordered pair; all bounded alternatives may obtain simultaneously, Work selection does not toggle them, and a changed admitted-part set reidentifies the whole Method or leaves the claim open. One part Method may have several whole Methods only through separately supported pairs and separately qualified whole constructions; no unique parent or closure property follows.
CC-B1.5-4Every serial, parallel, guarded, iterative, fallback, adapter, substitution, or typed-join use states a decidable claim and selects A.6.RCD’s lightest sufficient disposition. A relation kind and occurrence are required only after independent admission for a named occurrence-semantics use.
CC-B1.5-5The already identified candidate Method states whole-level participant meanings, applicability, preconditions, intended effects or preserved conditions, invariants, bounds, accepted inputs and outputs, failure and stop conditions, interface decisions, and reidentification rule before its composite qualification is accepted.
CC-B1.5-6Exposed, forwarded, and encapsulated interactions are distinguished because changing the reusable action or admissible boundary changes Method identity. A named caller system, planner system, auditor, substituting-method selection use, or assurance use determines whether the boundary account must be explicit or published; reliance does not create its identity effect.
CC-B1.5-7A boundary account states the interactions and conditions needed by its receiver. For publication, distinguish the MethodDescription edition, audience declaration, bounded-use declaration, expression and carrier; add a reusable form when its conformance matters. E.24.PUB supplies expression/bearing predicates and availability identity when needed. Publication Work and designation content remain separate claims.
CC-B1.5-8A selected A.22 structure has its four identity discriminators: constituents, obtaining relation occurrences, applied constraints, and use frame. Dated selection Work, an operation binding, or a persisted result episteme has separate grounds when that claim is needed. A sufficient local comparison requires no selected U.Structure.
CC-B1.5-9When the composite method needs a separate higher-level reidentification or emergence explanation, use B.2 in addition to the B.1.5 method reidentification rule.
CC-B1.5-10A temporal slice, episode, event-log segment, telemetry interval, engine stroke, detector component, or U.WorkPlan item is neither a Work part nor a Method part by appearance. Keep each with its subject pattern. A Work part enacts a submethod only through a separate A.15.1 enactsMethod occurrence; whole Work may enact the whole Method without mirrored Work parts.
CC-B1.5-11A needed order aggregation preserves B.1.4’s selected inputs, combining rule, order relations and required join or independence conditions. The OrderSpec may be stated in ordinary prose; use a separate record when the receiver needs it; neither adds Method identity nor establishes relation facts.
CC-B1.5-12Typed joins name the upstream intended-result meaning and downstream precondition, plus an adapter or governed correspondence when those meanings differ, and a failure route; signatures do not establish the holder’s ability.
CC-B1.5-13Dated Work, performing Systems, separately declared assignment species, assignment occurrences, obtaining F.6 attributions, resource use and costs, yields, dissipation, telemetry, results, and production, together with separate evidence-, publication-use-, evaluation-, delivery-, and acceptance claims, use their subject patterns and do not become Method identity fields.
CC-B1.5-14Assurance hooks name cutsets, fragile joins, adapter points, CL-sensitive mappings, and the envelope or claim scope consumed by B.3; no performance or quality claim follows from composition alone.
CC-B1.5-15A method-composition claim establishes no A.14 structural-component relation, work-part relation, or selected-structure identity unless the corresponding predicate separately obtains.
CC-B1.5-16Method parts, Work parts, common referents, method order, and temporal adjacency establish neither transformation parthood nor a composite transformation; missing transformation-composition governance returns missing-governor[transformation-composition] for the proposed whole and independently identified changes, without an atomism inference.
CC-B1.5-17A first–then or vertical account receives both checks: preserve every continuation condition as order or unfolding, and test whether several Methods contribute during the same bounded Work situation without one total sequence. Source order creates no level; simultaneous use creates no Method part, composite Method, Work part, or level.

B.1.5:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“The workflow diagram is the composite Method.”First govern the diagram as U.MethodDescription or another representation; identify the candidate and part Methods under A.3.1, then test methodPartOf, whole-forming claims at their A.6.RCD dispositions, whole semantics, boundary, and reidentification.
“Step A is part of the Method because it is a box.”Recover whether the box denotes a U.Method, description node, plan item, Work occurrence, claim, or lens expression; test methodPartOf only for an independently identified Method.
“Parallel branches can join because the picture rejoins.”State the independence, downstream precondition, join, any adapter or correspondence, and failure route in ordinary language; use A.6.RCD’s lightest sufficient disposition and open a relation kind only for an independently accepted occurrence-semantics need.
“The production plan lists five Methods, so the practice has five stages.”Preserve any setup, handoff, or continuation order. Then test the representative Work: Methods may contribute together in one Work whole or in overlapping Work occurrences. The plan’s row order establishes neither a total sequence nor a subject level.
“The selector table is the Method.”Use G.5 for the selector. Select an A.22 structure when the receiving use needs that organization and all four discriminators are established; otherwise retain the sufficient local comparison. A composite Method needs its construction and whole-level commitments.
“The run proved the method structure.”Record the run as U.Work; relate it to the method through enactsMethod and use evidence only through its governing relation. A successful run neither creates method parts nor settles reidentification.
“The phase is a method step.”Recover the subject: use the carrier’s identity rule plus proper A.14 PhaseOf for one unchanged non-Work individual, C.2.1 for distinct MethodDescription epistemes and any obtaining edition relation, or A.15.1 for Work temporal parts and occurrences. None is a Method part unless a U.Method and methodPartOf independently obtain; use B.2 only for a separately current whole-reidentification, supervision, or closure claim.
“The join improves throughput, so the method has emergence.”Name the measured characteristic, critical path, cutsets, typed joins, and assurance relation; open B.2 only when a separate whole-level reidentification claim remains.
“The boundary-account prompts define the Method.”Recover the Method and its construction facts first. The account describes those facts; a selected form constrains eligible expressions. Use E.24.PUB when the publication relation or form conformance matters.
“The boundary account is a nice diagram.”State the interactions and their conditions. If a receiver depends on publication, identify which description edition is available to which declared audience and use through which expression and carrier. Open E.24.PUB’s further predicates for the unresolved publication question.
“The same Work and referent make the transformations one composite.”Identify each transformation under A.3.4. Without a transformation-composition governor, return missing-governor[transformation-composition] for the proposed whole and independently identified changes; infer neither composition nor atomism.

B.1.5:9 - Consequences

B.1.5 buys inspectable Method composition without confusing the candidate Method, composition claim, MethodDescription, selected Structure, Work occurrence, resource use, and assurance argument. The practitioner can say which Methods are parts, which ordinary whole-forming claims and constraints qualify the candidate as composite, which interactions belong to its boundary, what Work enacts it, and where a stronger claim must stop.

The cost is proportionate explicitness: Methods, methodPartOf occurrences, whole-forming claim content, order and join conditions, interface decisions, whole semantics, and reidentification must be stated before the composite qualification can be relied on. Ordinary use can stop at local claims; reusable definitions, relation kinds, declarations, publication, and assurance are added only when a named receiver needs them.

B.1.5:10 - Rationale

The rationale is object separation. Paying this explicitness cost exposes brittle joins and accidental external dependencies at Method boundaries before someone relies on the composite claim. Order is semantic but not structural parthood. A method can be a non-agentive holon, but a step label, graph node, phase, source section, description constituent, plan item, or work part is not a method part until the U.Method and methodPartOf occurrence are recovered. Gamma_method concerns ways of doing; Gamma_work supports occurrence-side resource analysis; B.3 evaluates assurance; A.22 selects useful relation organizations; B.2 handles a separately current higher-level reidentification claim. None of those neighboring objects replaces the B.1.5 construction facts.

B.1.5:11 - SoTA-Echoing

The following published treatments provide bounded comparisons for Method composition. Their models illuminate distinctions; applying those distinctions to FPF Methods uses the construction and identity tests above.

Published treatment and its contributionUse in B.1.5Applicability limit
Case and decision models in CMMN 1.1 (2016) and DMN 1.5 (2024), object/event records in OCEL 2.0, and traces in OpenTelemetry 1.58.0 describe different objects. These named editions supply historical comparison examples; A.15 and A.15.1 govern the Work claims.Distinguish a reusable composition account from records about its enactment. Recover the Methods and construction facts, then use the Work or evidence predicates for what happened.A model or telemetry representation can support a claim without itself being the Method or establishing Method parts.
Bosman et al., “A Calculus for Scoped Effects & Handlers” (2024) separates syntax from handling semantics and provides explicit forwarding of scoped operations. Matache et al., “Scoped Effects as Parameterized Algebraic Theories” (2024) develops equational reasoning for scoped operations.Use these software examples to examine scope, typed joins, forwarding and boundary behavior. Explain the preconditions, result meanings and failure routes of the proposed Method composition in its domain.These calculi supply no general Method identity for manufacturing, clinical or organizational work. An FPF boundary change affects identity when it changes the reusable action or admissible boundary under A.3.1.
Gogioso et al., “Constructor Theory as Process Theory” (2023) connects abstract tasks to physical processes through a compositional formal treatment. A.3.1 develops the Method-side comparison.Retain the distinction between a specified task and a process that realizes it when examining composition and enactment.The formal bridge does not by itself identify an FPF Method part or dated Work; use their predicates.
Borgo and Righetti, “Towards Applied Constructional Ontology” (2025) examines choices and difficulties in applying constructional approaches to foundational ontologies. A.1 develops the construction-sensitive comparison.State constituents, construction facts and identity choices instead of treating a diagram or label as a constructed whole.Method composition retains its predicate. Its order is not structural parthood, and the source’s exploratory ontology comparison supplies no ready-made Method composition rule.

B.1.5:12 - Relations

B.1.5.CM constructs the prospective whole, constituent contributions, joins and boundary account that this qualification consumes. C.32.MWA.PP separately compares performance and provision arrangements. Useful cooperation or a shared provider does not supply a missing Method whole.

  • Uses A.1 for the general non-agentive-holon recognition boundary; A.1 does not supply Method-part or whole-forming facts.
  • Uses A.3.1 to identify the candidate Method and every part Method before B.1.5 tests the composite-method qualification; B.1.5 governs only MethodPartOfRelation and the composite-construction test.
  • Uses A.6.RCD for serial, parallel, guarded, iterative, fallback, adapter, join, substitution, and other whole-forming claims. Existing direct predicates, local compound claims, and reusable predicate definitions are valid stopping results; only a named occurrence-semantics need requires E.24 for a kind candidate and E.24.UK.
  • Uses A.6.REL only when an independently admitted relation kind has an obtaining occurrence whose identity a receiver consumes. B.1.5 does not manufacture occurrence semantics for ordinary claim content.
  • Uses C.2.1 to identify predicate-definition, signature, and MethodDescription epistemes and any later episteme with changed identity-bearing content. Uses EpistemeEditionRelation only when C.2.1’s historical-continuation predicate obtains; otherwise the later episteme is a non-continuing replacement. A predicate definition may satisfy ordinary A.6.0 U.Signature membership; only an admitted relation kind can have a RelationSignature.
  • Uses B.1.4 when the receiving question needs order aggregation or its specification, with the selected inputs, combining rule, order relations and required join or independence conditions. OrderSpec states the required ordering; it needs no separate record when ordinary prose suffices.
  • Uses A.3.2 and C.2.1 for MethodDescription claims and identity. Uses E.24.PUB when publication affects the receiving use: start with the edition, audience, bounded use, expression and carrier; recover further expression, bearing, form-conformance or availability predicates for the question that remains. Publication Work and designation remain separate.
  • Uses A.22.CGUS when a first–then, guarded, branching, or returning unfolding is the useful result; an unfolding position is not a subject level or evidence that all contributions are sequential.
  • Uses A.15, A.15.1, and A.15.2 for dated U.Work, enactsMethod, and plans; uses A.2, A.2.1, and F.6 for local system-role-kind and Method alignment, separately declared assignment species, assignment occurrences, and obtaining Work–assignment attributions. The Method does not act, and neither a system-role kind nor an assignment performs Work.
  • Uses B.1.6 and Gamma_work only for occurrence-side work-resource aggregation after the Work and resource relations are recovered.
  • Uses B.3 for cutset, weakest-link, CL-sensitive mapping, and assurance claims; composition alone supplies no assurance verdict.
  • Uses A.22 when the receiving use needs a selected organization and its four identity discriminators are established. Ordinary comparisons can finish without that claim; a dated selection occurrence has its separate Work grounds.
  • Uses C.13 only after B.1.5 supplies Method parts, whole-forming facts and constraints, and the whole reidentification rule; C.13 consumes those facts but does not create them or require one relation kind per fact.
  • Keeps A.14 structural-component parthood distinct from Method composition; uses B.3.5 only when its additional assurance profile is elected for the structural claim.
  • Uses B.2 when a separate higher-level reidentification or emergence-family explanation is current; ordinary composite-Method identity still needs its B.1.5 rule.
  • Uses G.5 when a Method-family registry, selector, fallback, or candidate-set decision is current but no whole construction is claimed.
  • Use C.29 for an unresolved mathematical representation, correspondence or transfer question; an adequate local calculation can suffice. Use A.6.1 for a needed law-governed operation declaration or application binding, and E.20 when a proposed change affects mechanism meaning, suite semantics, wiring, governing-definition assignment or citeable-token meaning.
  • Uses E.10 for method, step, process, workflow, ownership/stewardship, requirement, and source wording precision recovery.
  • Stops before any positive transformation-composition or transformation-part claim until a governor supplies participants, obtaining semantics, and occurrence identity.

B.1.5:End

Referenced in the corpus

162 literal mentions in other sections. Read their context to establish the relation.