FPF Reference

    C.30.TFS-REL:4.2 - Relation to functional structure

    Preface node heading:c-30-tfs-rel-4-2-relation-to-functional-structure:55606

    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

    FunctionalStructureView@Context under C.30.ASV may cite ArchitectureTransformationFlowStructureRelation@Context when a transformation-flow relation is being used. That relation does not make the selected E.18 structure a functional element and does not make a functional element identical with the system, module, method, or flow. It says that a functional structure view, functional behavior, or selected functional element corresponds to, is declared relative to, or positively co-refers with one E.18 selected structure, path, crossing, or valuation relation under a named context.

    FunctionalElement@Context is a view-local functional-structure record governed by C.30.ASV, not a new root kind. It is current only when C.30.ASV has a selected functional structure view, bounded context, functional behavior, and bearer or candidate-bearer locus. Its functional behavior may be a bounded U.Transformation or a compound TransformationFlowStructure; its transformer-side filler is recovered through A.3.4 when a transformer claim is current; its module relation is allocation or correspondence through A.6.M. A graph-shaped expression, path, valuation, or flow packet is therefore not the functional element by default.

    FunctionTransformationFlowRelationNote:
functionalStructureViewRef:
functionalElementRef?:
functionalBehaviorRef?: U.Transformation | TransformationFlowStructure
transformerSideFillerRef?:
candidateBearerRef?:
inputConditionRefs?:
outputConditionRefs?:
functionalPortRefs?:
transformationFlowStructureViewRef:
architectureTransformationFlowStructureRelationRef:
pathOrSliceRef:
crossingBundleRef:
correspondenceOrCoReferenceClaim:
preservedStructure:
lostOrHiddenStructure:
sourceReturnCondition?:
admissibleUse:
nonAdmissibleUse:

    Use this note when the practitioner needs to see whether the function-to-transformation-flow relation changes inspection, split, relation-making, downgrade, claim-governance assignment 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 bounded transformation and transformer slots, A.6.M for module-allocation claims and module-correspondence claims, and E.18 for selected transformation-flow structure.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)