#A.2.9:2 — Problem

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

#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: a concrete accountable subject performs the act (role or role-enactor), not a 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 is recognized inside a declared bounded context (the U.Work judgement context), not via U.ClaimScope (which expresses applicability of claims/commitments, not the judgement context for Work occurrences).
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-07-03 — upstream FPF commit f7c7e93f (github.com/ailev/FPF)