#A.2.9:1 — Problem frame

Preface node heading:a-2-9-1-problem-frame:6312

#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

FPF repeatedly needs to reference “someone said/did the approving/authorizing/declaring thing”:

• Role eligibility and enactability checklists often depend on the presence of an approval/authorization act within a freshness window.
• Governance patterns and boundary writing (A.6 stack) need provenance: “this obligation or commitment, or this separately represented granted permission, was instituted by that act”.
• Operational patterns need auditable notices (“depletion notice”, “override invoked”) whose existence and timing matter.

Without a first-class kind for such communicative Work and a separate way to describe each occurrence, authors tend to:

• attribute agency to descriptions (“the spec approves…”, “the interface guarantees…”),
• collapse “utterance text” and “speech act event”,
• leave provenance dangling as “if modeled”,
• encode gates as prose obligations, or treat obligations as gates.

This pattern admits U.SpeechAct as an explicit Work kind, identifies actual speech-act occurrences under it, and keeps their optional records separate from U.Commitment, utterance descriptions, and carriers.

---

Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)