FPF Reference

    C.3.A:B.8 Anti‑patterns & remedies

    Preface node heading:c-3-a-b-8-anti-patterns-remedies:39734

    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‑patternWhy it’s riskyRemedy
    “We tested one golden case.”Hides variant risk; ignores subkinds.Build a subkind‑indexed matrix; add boundary tests per column.
    “Latest data suffices.”Non‑deterministic; un‑auditable.Declare Γ_time windows; fail closed on expiry.
    “Tool is trusted, so we’re done.”Confuses TA with VA/LA; misses content risk.Keep TA separate; add VA proofs or LA tests as needed.
    Bridging without penaltiesUnderstates risk; mapping gaps surface laterApply scope‑bridge and kind‑bridge penalties to R; publish loss notes.
    Widening G to cover evidence gaps.Conflates applicability with available tests.Keep G honest; expand matrix or lower claim scope explicitly (ΔG−).
    Inferring scope from how many items matchScope is not the same as membershipKeep Scope (where it applies) distinct from membership (which items match in the slice).

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)