FPF Reference

    A.2.9:2 — Problem

    Preface node heading:a-2-9-2-problem:6840

    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

    How can FPF represent communicative enactments so that:

    1. Agency is explicit: an admitted accountable U.System performs the act under a covering role assignment, not a role value, assignment, document, spec, or interface.
    2. The act is locatable in time: the act has an explicit Window (and thus freshness can be evaluated).
    3. The act is locatable in meaning: the act satisfies a type defined by an exact recognition-taxonomy episteme under an effective reference scheme; no generic bounded-context participant or Work judgement-context field substitutes for that basis, and U.ClaimScope remains only a claim-applicability object when a receiving claim needs one.
    4. The act is auditable: it has at least one declared utterance description, evidence carrier, or both when used for gate checks or governance.
    5. Institutional effects are linkable: the act can institute (or update/revoke) commitments, role assignments, statuses, etc., by reference.
    6. Ambiguity is handled pragmatically: the model supports multi-function and multi-party communication without requiring full linguistic pragmatics.

    Last Updated: 2026-08-03 — upstream FPF commit 9dd92159 (github.com/ailev/FPF)