A.3.4.P:2 - Problem

Without this repair:

1. Source label becomes kind. “Pipeline”, “workflow”, “network”, “circuit”, or “process” is treated as the recovered FPF kind.
2. Selected structure becomes one actual transformation. A flow, path, network, or circuit expression is treated as one actual U.Transformation or as proof of transformation composition without the exact changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis. Identifying one occurrence at the resolution needed by the current use establishes neither finer transformation parts nor partlessness.
3. Method, mechanism, and work collapse. A method description, law-governed mechanism, work plan, dated work, or source diagram is selected by vocabulary rather than by current claim.
4. Functional wording overreaches. A system, module, port, interface, signature, or function label is treated as the transformation or as proof of functioning.
5. Mathematical expression becomes world-side ontology. A graph, morphism, algebra, category, path, network, or circuit expression is treated as the project-world change.
6. Description or evidence becomes transformation. A publication, dashboard, source span, proof, or evidence path is treated as the changed object or the change itself.