FPF Reference

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

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

    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 an actual ArchitectureRelation occurrence, bounded architecture claim, selected architecture-relevant structure, exact architecture structural view, functional-structure view, transformation-flow-structure claim, or conditional ArchitectureDescription use depends on one or more of the following:

    • TransformationFlowStructureRef;
    • TransformationFlowStructureNetworkRef, when architecture use selects an E.18.NET-conforming network;
    • PathId or PathSliceId;
    • CrossingBundleRef;
    • flow valuation over the U.Transfer relation;
    • edition, plane, or context pin;
    • no-hidden-scalarization or set-return discipline;
    • a correspondence claim or independently governed relation between functional structure and transformation-flow structure;
    • a generated or extracted relation graph used as candidate input for the architecture-to-transformation-flow use.

    If the sentence only says that Work occurred, use A.15.1 or the governing Work pattern. If it says that an actual referent changed, use A.3.4 before citing a U.Transformation. If it only says that one selected TFS exists, use E.18; if it only says that one independently identified E.18.NET-conforming TFS network is selected, use E.18.NET. 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 use depends on one A.22-selected CGUS qualified under E.18.3. The ref names that selected CGUS; its E.18.3 account separately names one independently identified E.18 substrate branch and the exact positions, bindings, and already-obtaining occurrences the CGUS uses. Architecture, decision, work, feedback, narrative, or refresh values connect only through exact already-obtaining supporting relations, with predicate-definition content and current facts when the claim needs them; the pattern reference adds no connection relation. 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 trace.

    Last Updated: 2026-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)