FPF Reference

    C.30.TFS-REL:4.1 - Use trigger

    Preface node heading:c-30-tfs-rel-4-1-use-trigger:58996

    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 only when a ArchitectureOf@Context claim being made, selected architecture-relevant structure, architecture structural view, functional-structure view, transformation-flow-structure claim, or conditional ArchitectureDescription@Context use depends on one or more E.18 objects:

    • TransformationFlowStructureRef;
    • PathId or PathSliceId;
    • CrossingBundleRef;
    • flow valuation over the U.Transfer relation;
    • edition, plane, or context pin;
    • no-hidden-scalarization or set-return discipline;
    • correspondence between functional structure and transformation-flow structure;
    • generated or extracted relation graph used as candidate input for the architecture-to-transformation-flow relation.

    If the sentence only says that work occurred, use A.15 or the governing work pattern. If the sentence only says that a selected transformation-flow structure exists, use E.18. If the sentence uses a graph-shaped expression as mathematical description, use E.18.2. If it relies on a mathematical lens, use C.29.

    Use transformationFlowUnfoldingStructureRef? only when the architecture relation depends on an E.18.3 transformation-flow unfolding structure: the selected E.18 structure is being unfolded toward next architecture, decision, work, feedback, narrative, or refresh uses under constraints and direct exits. Generic architecture use of a constraint-governed unfolding structure belongs in C.32.P2S or the direct C.30 architecture governing pattern; this pattern keeps only the architecture-to-transformation-flow relation.

    Last Updated: 2026-07-12 — upstream FPF commit 44dd8818 (github.com/ailev/FPF)