A.6.C:5.1 — Tell
Preface node
heading:a-6-c-5-1-tell:16231
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 boundary contract-language leaves a consequential ambiguity, recover the claim and referent, then answer only the live questions below. Keep ordinary metonymy when its capable participant and relation are locally recoverable; a literal act or individual commitment needs that participant and the governing conditions.
- What was promised? State the promise-content claim if one exists.
- What was said, published, or instituted? Identify only the asserted speech act, description/publication objects and institutional effects, under the conditions in §4.1.
- What governance or permission-looking claim exists? State either a generic D prescription with its normative source and applicability, an individual D claim about an 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 missing governor. - What happened, what followed, and what supports reliance? State dated Work, each current result/change/delivery/acceptance claim, and each current evidence-use or reliance claim separately; omit absent claims.
When acceptance or the work still due depends on how undertakings, conditions or acts fit together, use §4.1 to establish the required connection. This includes one order with several required acts. Identify what was accepted and what remains open or due.
When those answers need stable reuse, decision, audit, dispute, or cross-face projection, write them in the one A.6.B Claim Register: one atomic statement, direct object, subject assertion, non-semantic pattern locator, and quadrant per row. Otherwise stop with the repaired atomic prose. Faces cite reused claim IDs or canonical locations; they do not create another bundle record.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)