#A.2.9:9 — Consequences

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

#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.
• Prevents recurring category errors: “documents promise”, “interfaces commit”, “logs prove”.

Trade-offs / mitigations

• Reliance-bearing uses require a small structured SpeechActRecord plus adequate evidence; ordinary occurrence talk needs no record when no later claim must cite it.
• Requires context-local SpeechActTypeRef registration; mitigated by starting with a small set (Approve, Revoke, Publish, Notify, Authorize) and extending as needed.

---

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