A.2.9:3 — Forces

Preface node heading:a-2-9-3-forces:9239

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

ForceTension
MinimalityThe account should serve routine use without requiring a full pragmatics or legal-instrument model.
AuditabilityIf used as a gate, it must be evidence-backed; but not all communicative acts are equally observable or retainable.
Interpretive localityRecognition and institutional force depend on exact taxonomies, schemes, and current policies; F.9 is needed only when a receiving use crosses local meanings.
Multi-party realityMany boundaries are multiparty (protocols, organizations); dyadic “speaker-hearer” is too narrow.
Multi-function realityOne utterance can carry multiple recognizable functions; “one act = one force” is often false.
Separation disciplineMust preserve kind ≠ actual act occurrence ≠ SpeechActRecord ≠ utterance description ≠ carrier or trace.
Use proportionalityA receiving-use judgement must remain useful without a full occurrence record, while audit or institutional reliance needs exact Work, assignment, Method, taxonomy, and evidence, plus a policy when recognition or institutional force depends on it.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)