#A.2.9:9 — Consequences

Preface node heading:a-2-9-9-consequences:7689

#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

Benefits

• Makes approvals/authorizations/notices first-class and queryable, enabling clean RSG checklists and guard rules.
• Provides stable provenance: commitments, granted permissions, and status transitions can cite the instituting act explicitly.
• Makes the actual performer recoverable in occurrence and institutional-provenance claims.
• Lets a practitioner judge one named receiving use and repair the smallest blocker without first building a complete occurrence record.
• Keeps observed response, achieved use, later action or change, causal contribution, and permission or admissibility as separately testable questions.

Trade-offs / mitigations

• A receiving-use judgement may remain conversational when no later claim must cite it. A reliance-bearing use requires a small structured SpeechActRecord plus adequate evidence only when the occurrence itself must remain addressable.
• Requires one exact recognition-taxonomy episteme and effective reference scheme for SpeechActTypeRef; mitigated by starting with a small set (Approve, Revoke, Publish, Notify, Authorize) and extending that taxonomy deliberately.

---

Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)