FPF Reference

    A.2.9:7 — Conformance Checklist (normative)

    Preface node heading:a-2-9-7-conformance-checklist-normative:5632

    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

    1. CC‑A.2.9‑1 (Accountable performer). A normative U.SpeechAct record MUST identify performedBy as an accountable RoleAssignmentRef and MUST NOT use a specification episteme, interface-description episteme, or document-carried episteme as performer.
    2. CC‑A.2.9‑2 (ActTypes declared). A U.SpeechAct record MUST include at least one SpeechActTypeRef recognized in its judgement context.
    3. CC‑A.2.9‑3 (Window explicit). A U.SpeechAct record MUST have an explicit window (or inherit a window from its parent work record) so freshness and gating can be evaluated.
    4. CC‑A.2.9‑4 (Observable when used for gating/provenance). If a speech act is cited by a checklist/guard or by U.Commitment.source.speechActRef, it SHALL have at least one utteranceRef or carrierRef that supports observation/audit in the given context; evidence‑critical uses SHOULD anchor at least one carrier via SCR/RSCR per A.10.
    5. CC‑A.2.9‑5 (Effects by reference). If the act is intended to institute/update commitments/roles or statuses, those effects SHOULD be referenced in institutes.* by stable IDs.
    6. CC‑A.2.9‑6 (Bridge-only cross-context use). If a SpeechActRef is interpreted for gating/provenance in a different bounded context than the act’s judgement context, the referencing object MUST cite the Bridge/policy that licenses that cross-context interpretation (no “same label implies same force”).

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)