#A.2.9:4.5 — Multi-function and multi-party support (normative)

Preface node heading:a-2-9-4-5-multi-function-and-multi-party-support-normative:7531

#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

• Multi-function: actTypes is a set. When one actual communicative Work performs several recognizable functions, one speech-act occurrence carries all satisfied actTypes; taxonomy tokens do not multiply the Work. Identify several occurrences only when the occurrence-identity rule in §4.1 finds distinct world-side grounds. Their records may share utterance or carrier references without thereby becoming the same occurrence. If the named use still admits competing segmentations, cite its continuity or segmentation rule or leave the boundary unresolved. Institutional effects remain separately referenceable (SA‑C5).

• Multi-party: addressedTo is a set. Its optional members may be parties, exact local system-role kinds, or exact obtaining occurrences of directly declared U.SystemRoleAssignment species. State which branch each addressee uses. Being addressed makes none of them the performer and establishes no authority, commitment, permission, responsibility, or institutional effect.

---

Last Updated: 2026-08-30 — upstream FPF commit e400eab3 (github.com/ailev/FPF)