#A.2.9:1 — Problem frame

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

#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/commitment/permission was instituted by that act”.
• Operational patterns need auditable notices (“depletion notice”, “override invoked”) whose existence and timing matter.

Without a first‑class kernel object for such communicative events, 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 makes “speech act” an explicit, queryable Work‑kind with clear boundaries to U.Commitment and to utterance surfaces.