FPF Reference

    C.30.TFS-REL:6 - Bias-Annotation

    Preface node heading:c-30-tfs-rel-6-bias-annotation:62752

    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

    Lenses tested: Arch, Onto, Epist, Prag, Did, Gov. Scope: architecture-to-transformation-flow uses of E.18 TFS or E.18.NET network objects.

    Bias riskMitigation
    Structure-or-description-as-architecture biasDirect architecture relations and bounded claims stay with C.30, descriptions with C.30.AD, representations with C.29, mathematical descriptions with E.18.2, math-lens uses with C.29, and structural views with C.30.ASV/E.17.0.
    Function-flow/change collapseRequired functional content, selected transformation-flow structure, and actual A.3.4 transformation remain separate. Functional and flow structures are related, not identical by default.
    Non-flow claim overreadThe relation table assigns non-flow claim kinds to their governing patterns.
    Mathematical overreadMathematical-lens use of a graph or valuation is governed by C.29.
    Check-only biasConformance checks include repair actions and stop conditions.

    This checklist verifies the preceding guidance after the practitioner has chosen the selected repair action; it is not a required project control form and not a substitute for the card, note, use record, direct relations, or repair guidance above.

    Last Updated: 2026-07-31 — upstream FPF commit 1eb56cd0 (github.com/ailev/FPF)