| Cue word as ontology | “Pipeline”, “process”, “network”, or “circuit” is treated as the FPF kind. | Recover the current object: U.Transformation, TransformationFlowStructure, mathematical description, method, work, publication, or direct subject pattern. |
| Replacement by smoother umbrella | “Process” is replaced with “flow” or “operation” without recovered kind. | Run the replacement through the same recovery. If the kind is still hidden, leave it unresolved. |
| Network head inflation | Frequent network or circuit wording becomes a peer durable head. | Use network or circuit as structure form, topology label, mathematical-expression family, domain label, or subject-domain system only when recovered by value. |
| Selected structure as transformation composition | Common membership in one flow, path, network, circuit, or pipeline is treated as a composite transformation, transformation-part relation, or proof of indivisibility. | Use E.18 only to position, relate, or locate transformation loci and adjacent governed values. Ground every actual U.Transformation independently under A.3.4; common structure membership establishes neither composition, parthood, nor partlessness. |
| Workflow as performed work | A workflow diagram or process model is treated as dated work. | Use A.3.2, E.18, or C.2.P.DR for the description or structure; use A.15.1 only for dated work. |
| Function as proof of behavior | A module, port, participant, assignment occurrence, or “transformer” label is treated as proof of actual change or action. | Recover the actual transformation basis. For performed Work, recover each precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is current, and name the required separate Work-to-change relation. Otherwise use the exact participant, operation-application, functioning, causal, or other direct actor-side relation. |
| Architecture influence as action | A manufacturing or certification organization, design organization, Method or Method family, toolchain, communication System, selected structure, or other value is called the actor because it constrained or enabled a candidate. | Recover the value’s exact kind first, then only its exact architecture, Work, communication, constraint, or candidate-synthesis relation. For an actor claim, apply the separate performed-Work or non-Work test in 4.4. |
| Publication as change | A diagram, proof, dashboard, or source span is treated as the changed object or change occurrence. | Recover the cited object’s kind and use under its subject pattern; use A.3.4 for any claimed actual change. |