FPF Reference

    A.6.C:5.1 — Tell

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

    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. What was promised? Record the exact promise-content claim if one exists.
    2. What was said, published, or instituted? Give the speech-act Work, each description/publication object, and each institutional effect its own row and subject pattern.
    3. What governance or permission-looking claim exists? Record either a generic D prescription with its exact normative source and applicability, an individual D claim about an exact obtaining commitment with its actual bearer and institution basis, or the selected A6-AW-* claim in its own quadrant. State responsibility separately under its admitted domain predicate or return its exact missing governor.
    4. What happened, what followed, and what supports reliance? Record dated Work, each current result/change/delivery/acceptance claim, and each A.10 evidence claim separately; omit absent rows.

    Write those answers in the one A.6.B Claim Register: one atomic statement, direct object, exact subject assertion, non-semantic pattern locator, and quadrant per row. Faces cite the claim IDs; they do not create another bundle record.

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