A.15.6:4.2 - Recover a process concern through U.Method, a selected U.Structure, or TransformationFlowStructure
When the question is about repeatability, ordering, throughput, variation, control, or improvement, select the subject that the claim actually concerns:
U.Methodfor the reusable way of doing;- a
U.Structureselected underA.22when the organization of already identified method-side objects and relations changes the next question or admissible action; TransformationFlowStructurewhen the question concerns the organization of transformation flows.
Keep a measure, evaluation result, relation occurrence, event collection, or dated Work as its own subject when that is what the claim asserts.
For a method-side U.Structure, identify the constituents, the selected obtaining relations, the applied constraints, and the frame that states the selection question, permitted action, and prohibited overread. Only then may MethodRelationStructure serve as a local designator. If any discriminator is absent, keep the direct relations unbundled.
A dated U.Work occurrence supports only the fact recovered from it. To show Method enactment, use A.15.1 to state which Method that Work enacts. To show one operation application, name the reusable A.6.1 declaration, the particular application, and its typed argument or result bindings. A shared label, compatible result, trace, record, order, or timestamp establishes neither fact and does not retype Work as a Method or structure.
Do not force multi-object event data into one preselected case key or one flattened sequence. Preserve the relevant object and event relations, then select a process execution, grouping, query, or constraint only when the current use needs it. The selection is a modeling decision. A selection-result episteme concerns the observed material and serves as evidence only through an independently obtaining evidence-use relation; neither the selection nor that evidence use establishes Method identity. Stop when the reusable way, selected organization, or transformation-flow question has been answered.