FPF Reference

    A.6.C:6 — Bias-Annotation

    Preface node heading:a-6-c-6-bias-annotation:9634

    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: Gov, Arch, Ontological and Epistemic, Prag, Did. Scope: Universal for “contract talk” in boundary descriptions.

    • Gov bias: prefers explicit accountability and adjudication hooks; increases clarity but adds authoring overhead.
    • Arch bias: optimises evolvability by preventing hidden coupling (contract soup) across stack layers.
    • Ontological and Epistemic bias: enforces EntityOfConcern, Description episteme, and carrier separation; discourages “interface-as-agent” metaphors in Tech prose.
    • Prag bias: accepts that “contract” is common vocabulary; offers a disciplined rewrite rather than prohibition.
    • Did bias: aims to be teachable via repeated unpacking examples across boundary types.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)