FPF Reference

    C.30.TFS-REL:8 - Common Anti-Patterns and How to Avoid Them

    Preface node heading:c-30-tfs-rel-8-common-anti-patterns-and-how-to-avoid-them:62256

    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

    Anti-patternSymptomRepair
    Structure-as-architectureThe E.18 selected transformation-flow structure is called the whole architecture.Use C.30 for the grounded architecture claim, selected architecture-relevant structure, or conditional architecture description, and keep this relation only for the transformation-flow relation.
    Unnamed network as architecture bearerA connected network or its graph is assigned maintainability, capability, responsibility, agency, or production without one containing holon or explicit participating architecture claims.Select the named-containing-holon branch or the explicit inter-holon branch, restore every characteristic to a named bearer, and keep the graph or record outside architecture identity.
    Graph-description-as-functional-architectureA graph-shaped mathematical description or diagram is treated as the functional architecture itself.Split functional structure, selected transformation-flow structure, mathematical description, and publication face; add correspondence when needed.
    Flow-as-work-logPath or slice wording is treated as work occurrence.Assign occurrence or result claims to A.15 or P2W and keep E.18 to selected structure, path, slice, or valuation.
    Crossing-as-gate-resultA crossing relation is treated as gate passage.Assign gate-decision claims to A.21 and keep crossing relation under E.18.
    Valuation-as-scoreA flow valuation is used as a generic architecture score.State E.18 valuation and set-return discipline; assign measurement, characterization, selection, or candidate-set claims to C.16 or an admitted governing pattern when those claims are being made.
    Generated relation-graph proofA code-agent relation graph or probe output is used as proof of architecture understanding or safety.Recover the source publication or codebase edition, extraction or probe locus, relation observation class selected from {observed, inferred, unknown}, hidden structure, and evidence or assurance pattern governing the claim applications.
    Prompt-data-tool flow as authority proofA prompt, data, or tool-flow diagram is treated as permission for tool action or proof that authority is safe.Keep the diagram as a transformation-flow relation or E.18.2 mathematical description. A path from untrusted content to tool action is governed by SecurityTrustBoundaryStructure, C.24, E.16, A.20, or A.21 when those claim kinds are being made.

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