B.1.5:2 - Problem
Without B.1.5:
- Source-wording composition. “Step”, “stage”, “activity”, “task”, “procedure”, “workflow”, “pipeline”, or “algorithm” wording is accepted as method composition without recovering the actual objects.
- Description-as-method. A workflow diagram, BPMN model, code repository, proof script, table, checklist, or graph path is treated as the composite method itself.
- Order as mereology.
SerialStepOf,ParallelFactorOf, guarded choice, or fallback relation is placed in a structural part-whole chain. - Typed joins disappear. One submethod’s intended result is assumed to satisfy the next submethod’s precondition without an adapter method, governed correspondence or equivalence, and an explicit failure route.
- Interface exposure is hidden. Callers rely on internal interactions that should be encapsulated, or fail to see interactions that the composite method must expose.
- 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.
- 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.
- 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.
- 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.