COMMUNICATION-FOR-USE — Make communication useful, then learn from what happens

Preface node heading:communication-for-use-make-communication-useful-then-learn-from-what-happens:726

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

  • Situation: A report, model, message, or answer seems clear, but its intended use and evidence are unclear, including whether its producer can use it later.

  • Question: Who should understand or do what with it, what evidence is enough, and what should change if that use is not achieved?

  • First useful result or blocker: A supported decision to keep or repair it, change prerequisites or a future use, or stop, with evidence, causation, and permission limits.

  • Start with: Use A.2.9 to evaluate the communication against what its recipient should understand or do. Distinguish the act of communicating from its wording and medium, and interpretation from response, later action, world change and causal contribution.

    Choose the repair by its object: A.6.3.CR for wording, A.6.3.RT for representation, A.6.3.NAR for narrative, E.17.EFP for explanation or E.24.PUB for publication. Use A.10, C.28 or C.11 when you need to establish evidence, causation or a comparison of repair options, respectively. A repair may change prerequisites, medium, interaction or future use. Check authority, consent and admissibility separately.

  • Stop or return: Stop when the named use has enough support or a blocker is explicit. Preserve the earlier intended use when interpreting the response; revise a future use when warranted. Response or silence alone proves neither meaning, success, causation, authority, consent, nor permission.


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