C.30.TFS-REL:4.2 - Relation to functional structure
Preface node
heading:c-30-tfs-rel-4-2-relation-to-functional-structure:78526
What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
Content
A FunctionalStructureView under C.30.ASV may cite ArchitectureTransformationFlowStructureRelation when a transformation-flow use is current. That record does not make the selected E.18 structure a functional element or actual transformation, and does not make a functional-element claim identical with the system, module, method, bearer, or flow. It states a bounded claim or trace that functional-view content corresponds to, or is declared relative to, one E.18 selected structure, member-local path, crossing, or valuation. Positive co-reference states that the functional-structure and flow-structure designations refer to the same selected U.Structure.
actualTransformations, transformerSideSystems, and the single transformerSideSystem in the note below use the direct-value designation and external-address resolution rules in C.30.ASV:4.6.
Keep the same three branches used by C.30.ASV:
functionalBehaviorClaimRefsandrequiredOrDesiredEffectClaimRefsremain C.2.1 claim content under their requirement, architecture, capability, method, functional-view, or other direct owner;actualTransformationscite only independently identified A.3.4 occurrences with changed referent, boundary or extent, boundary conditions, before/during/after facts, and continuity or reidentification basis;selectedTransformationFlowStructureRefscite E.18 structures, which may organize several independently identified transformations and transfers but are not themselves required effects or actual transformations.
A FunctionalElementClaim is a bounded C.2.1 claim about one selected functional structure. Its bearer or candidate-bearer locus, capability, port, allocation, transformation, and correspondence refs retain their direct owners. A graph-shaped expression, path, valuation, required-effect statement, or flow packet is therefore not the functional element by default.
Required-cooling-effect / later-actual-cooling countercase. RequiredCoolingEffect-1 can require Rack 7 to be below 30 °C and can correspond to a selected cooling-flow structure before any change occurs. In that first use, fill requiredOrDesiredEffectClaimRefs and the selected TFS fields; leave actualTransformations empty.
A later Rack7CoolingTransformation-42 is actual only when A.3.4 fixes Rack 7 as the changed referent, its thermal boundary and operating/ambient conditions, 38 °C before facts, heat-removal during facts, 27 °C after facts, and continuity or reidentification of Rack 7.
Apply the requirement to the rack and period it names. A reliable reading of 27 °C establishes “below 30 °C at the specified instant” when it belongs to that rack and instant. For “below 30 °C throughout the shift,” one reliable 38 °C reading within the shift already establishes a violation. A reading before the shift leaves that guarantee open. Temperature and net heat removal can agree under two different cooling routes. Observed transfer through the named route can establish its participation. To decide whether that route was necessary for bringing the rack below 30 °C, compare what would have happened with the other heat exchanges but without that transfer.
Use this note when the practitioner needs to see whether the function-to-transformation-flow relation changes inspection, split, relation-making, downgrade, selection of the governing pattern for the claim named by value, candidate generation, or stop.
Use C.30.ASV for the functional structure view, A.6.F for function-like wording recovery, A.3.4 for an actual transformation, A.6.M for module-claim repair and the direct allocation/interface owner, and E.18 for selected transformation-flow structure.
FunctionTransformationFlowRelationNote is the one-TFS form. When architecture use selects a network, use the top-level ArchitectureTransformationFlowStructureRelation and the branch in C.30.TFS-REL:4.4a. Name a member TFS in this note only when the function correspondence is to that member; membership in the selected network alone does not create a function correspondence.
When several transformation-flow variants are kept or compared as candidate architecture inputs, keep each selected transformation-flow structure, path, crossing, valuation, graph-shaped expression, or mathematical description under E.18, E.18.2, and this record. Apply C.32 only to the architecture candidate palette that uses those selected structures. The graph, path, and flow description do not become architecture adequacy, evidence, assurance, gate passage, selected-set result declaration, publication occurrence, or decision by serving as a candidate input.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)