A.2.9:12 — Relations
Preface node
heading:a-2-9-12-relations:7717
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
Uses / builds on
- Uses A.13 and A.15.1 (
U.Work) for the independent actual-occurrence backbone: exact actual performer System; local agential kind and criterion; classification; obtaining assignment, scope, working situation, and window; adequate core evidence and only a conditionally consumed profile; grounded communicative history; enactedU.Method; temporal extent; and at least one obtaining locally declared containing-System relation. Uses F.6 only afterward for a preciseperformedUnderAssignmentclaim through the same obtaining assignment. Uses a separate optionalmethodDescriptionRefonly when the receiving claim needs that episteme. - Uses A.7 for the strict actual-act≠record/description≠carrier split.
- Coordinates with A.2.6 for scope/window discipline.
- F.18 can serve as a lexical entry point for naming
U.SpeechActand “utterance” in the promise/utterance/commitment triad.
Used by
- A.2.8 (
U.Commitment) when an exact policy treats the speech act as the required instituting basis and the direct commitment predicate independently holds, and A.2.8.PER when aGrantedPermissionRelation@Contextindependently obtains with this act asinstitutingSpeechActRef. - A.2.5 (RSG checklists/guards) when “presence of authorization/approval act” is a criterion.
- A.6.C for unpacking promise, approval, guarantee, and agreement-like boundary wording while preventing episteme-as-agent claims and preserving provenance.
Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)