#A.6.C:5.1 — Tell

Preface node heading:a-6-c-5-1-tell:9565

#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

If you use contract-language for a boundary, do not treat “the interface or specification” as an acting system. Instead:

1. Identify the promise content (promise content) being promised,
2. Identify the accountable Commitment holder(s) (accountable role assignments or admitted acting systems),
3. Identify the Utterance surfaces that publish the boundary (signature or mechanism descriptions plus MVPK views),
4. Identify the Performed work and evidence carriers that could adjudicate whether commitments were met,
5. Classify each claim through L/A/D/E and reference across quadrants rather than paraphrasing.

---

Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)