FPF Reference

    C.30.TFS-REL:4.6 - Lowering and currentness conditions

    Preface node heading:c-30-tfs-rel-4-6-lowering-and-currentness-conditions:62199

    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

    Lower, narrow, or reopen the relation at the smallest changed locus when:

    • E.18 one-TFS structure, path, crossing, or flow-valuation semantics change;
    • E.18.NET network identity, direct membership, exposed positions, exact cross-member relations, or nested-row locator resolution changes;
    • the selected network architecture branch or any containing or participating architecture claim used by that branch changes;
    • edition, plane, context pin, set-return, or no-hidden-scalarization discipline changes;
    • source publication or graph edition, path slice, relation observation class, edition or context pin, unexplored region, or hidden relation-structure return condition changes;
    • the C.30 architecture locus, selected architecture-relevant structure, architecture structural view, conditional architecture description, or C.30.ASV relation changes;
    • functional-to-transformation-flow correspondence changes;
    • a non-flow claim is being made and is governed by C.30.TFS-REL:4.3 rather than by this relation;
    • C.29, C.16, C.28, A.10, G.6, B.3, A.20, A.21, A.15, C.30, C.30.ASV, A.6.F, C.30.STRAT, E.18, or E.18.NET changes the governing boundary used by the relation.

    Admissible repair results are: update the affected TFS or network reference, network branch, or row locator; add or change correspondence or the hidden relation-structure return condition; narrow admissible use; keep the one-TFS claim inside E.18 and the network claim inside E.18.NET; keep the mathematical-description claim inside E.18.2; keep the math-lens-use claim inside C.29; apply the governing pattern to a non-flow claim; lower to quote-only or reduced-use cue; or block the architecture-to-transformation-flow use.

    Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)