FPF Reference

    C.30.TGA-FLOW-REL:1 - Problem frame

    Preface node heading:c-30-tga-flow-rel-1-problem-frame:54370

    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

    Use this pattern when an architecture discussion depends on a Transduction Graph Architecture (TGA) graph, path, path slice, crossing, flow valuation, edition pin, plane pin, context pin, or no-hidden-scalarization claim.

    The first useful move is small. ArchitectureFlowStructureRelation@TGA is a C.30-side relation record for a relation being used between ArchitectureOf@Context, selected architecture-relevant structure, architecture structural view, or conditional ArchitectureDescription@Context use and the E.18 graph, path, crossing, or flow-valuation relation being used for flow or transduction structure. It names the architecture locus, selected structure or view reference when used in the relation, conditional description reference when durable description use is being made, the E.18 object, correspondence or source-return condition when used in the relation, and the admissible architecture use.

    ArchitectureFlowStructureRelation@TGA:
architectureClaimRef?:
selectedArchitectureStructureRefs?:
architectureStructuralViewRef?:
architectureDescriptionRef?:
functionalStructureViewRef?:
flowTransductionStructureViewRef?:
transductionGraphRef?:
selectedPathOrSliceRefs?:
crossingBundleRefs?:
flowValuationRefs?:
correspondenceRefs?:
sourceReturnCondition?:
admissibleUse:
nonAdmissibleUse:

    Ordinary minimum: name at least one architecture-side reference (architectureClaimRef, selectedArchitectureStructureRefs, architectureStructuralViewRef, or architectureDescriptionRef when durable description use is being made), at least one E.18 object reference (transductionGraphRef, selectedPathOrSliceRefs, crossingBundleRefs, or flowValuationRefs), the architecture-flow FlowTransductionStructure, one blocked overread, and stop or governing-pattern application. Use functional-structure, flow-structure, crossing, flow-valuation, correspondence, and source-return fields only when they change the next architecture move. All other fields are conditional and may be not used.

    Use this relation only when a grounded architecture claim, selected architecture-relevant structure, architecture structural view, functional-architecture view, flow-structure claim, or conditional architecture-description use depends on an E.18 graph, path, crossing, or valuation relation. Stop when the architecture-flow relation and non-admissible uses are clear. If another claim is being made, that claim is governed by its governing pattern and this relation remains only the architecture-flow relation.

    What goes wrong if this pattern is missed: a TGA graph becomes functional architecture, whole architecture ontology, performed-work occurrence, work-result record, proof, or project decision by appearance.

    What this buys in practice: the practitioner can use E.18 for flow or transduction structure while C.30 remains the grounded architecture and selected-structure adequacy locus and C.30.ASV remains the architecture-structural-view locus.

    Not this pattern when the question under repair is a graph, path, crossing, or flow valuation without a relation being used for grounded architecture adequacy, conditional architecture-description use, or an architecture structural view. Use E.18 directly. If the question under repair is an architecture claim or durable architecture description without an E.TGA graph claim, path claim, or crossing claim kind, use C.30. If it is a functional view without flow relation or TGA claim kind, use C.30.ASV and A.6.F. If another claim being made is present, use the governing pattern and keep C.30.TGA-FLOW-REL only to the architecture-flow relation.

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)