FPF Reference

    A.2.9:5.1 — Tell (universal rule)

    Preface node heading:a-2-9-5-1-tell-universal-rule:7563

    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

    When a named receiving use is current, first state who should understand or do what, what evidence would be enough, and the smallest repair or stop. Keep the act of communicating, its wording and medium, observed response, achieved use, later effect, causal contribution, and authority or permission questions distinct.

    When governance or gating depends on “someone said or did X”, first identify that saying or doing as SA : U.SpeechAct through the A.13-qualified performer, grounded communicative history, Method, extent, and containment required by A.15.1. Then, if the gate relies on the exact assignment under which it was performed, establish F.6 separately through the same A.13 assignment. Add a SpeechActRecord only to state relied-on claims about the already admitted act, and keep any MethodDescription, optional channel, utterance text, and carriers separate. If the occurrence institutes an obligation, recommendation-as-duty, or prohibition, cite a separately obtaining U.Commitment; if it institutes strong permission, cite a GrantedPermissionRelation@Context. The act institutes neither effect without an applicable policy or rule and independently satisfied conditions.

    Receiving-use worked slice. An engineer sends a threshold-change note to an operator. The named use is that the operator can identify the new threshold and the next safe action; the engineer should also be able to recover the reason for the change later. The operator replies “Got it” but updates the wrong parameter. That reply is evidence of a response, not achievement of the named use. The parameter update is a later action and world change; it does not by itself show that the note caused the change. Use A.10 when the evidentiary claim needs support and C.28 before claiming causal contribution.

    Persistent observation-only record slice. After A.13 supplies the performer basis and A.15.1 independently admits SA-Threshold-Change-17 : U.SpeechAct, a later review needs a durable observation that the threshold note occurred but makes no claim about the exact assignment under which it was sent. SA-Threshold-Change-17-Record : SpeechActRecord states the occurrence and actual-performer references, actual Method and containment references, act window, recognition taxonomy and scheme, act type, utterance-description locator, and carrier; it sets reliancePosture = observationOnly and omits performedUnderAssignmentRef. This record can preserve the observation and support receiving-use replay, but it cannot satisfy a guard, gate, or claim that depends on exact assignment-bound attribution. If that use later becomes current, establish F.6 for the already admitted act through the same obtaining A.13 assignment and add the resolving reference.

    The smallest repair may be a clearer threshold sentence or a changed table, followed by evidence that addresses the named use. If the operator lacks permission to make the change, return that blocker instead of repeating the message. If a later need adds audit use, apply it to later communication or a separately named reevaluation. It does not turn “Got it” into achievement of the earlier use.

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