FPF Reference

    C.3.A:A.1 Purpose & fit

    Preface node heading:c-3-a-a-1-purpose-fit:40352

    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

    What this solves. Regulations and standards name classes of things (“Adult person,” “Class II medical device,” “Personal data,” “Lease”). In one context they are native; in another they are foreign. Without typed reasoning, teams either (a) hand‑translate terms (silently changing meaning), or (b) reduce everything to Context labels (“domain = EU”), which cannot be checked by guards.

    What we add.

    1. Model regulatory categories as Kinds (with KindSignature and ⊑),
    2. map them across Contexts with KindBridges and type‑congruence CL^k,
    3. express Claim scope (G) over Context slices that explicitly list jurisdiction, version, and a time selector (Γ_time), and
    4. apply R‑penalties (Ψ(CL^k)and, if scope is bridged,Φ(CL)) while keeping F and G unchanged.

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