FPF Reference

    A.2.9:7 — Conformance Checklist (normative)

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

    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 (Occurrence, performer, and assignment). One actual Work individual is admitted as SA : U.SpeechAct; its performer is an admitted accountable U.System, and the exact obtaining U.RoleAssignment has that system as holder and exposes its own role value, role-taxonomy episteme, effective reference scheme, and covering extent. Any SpeechActRecord states those as claims and MUST NOT make the assignment, role value, organizational label, episteme, or carrier the performer.
    2. CC‑A.2.9‑2 (Exact Method and auxiliary description). The actual occurrence independently satisfies enactsMethod -> U.Method. A current methodDescriptionRef resolves to a separate C.2.1 episteme used to identify, constrain, or justify that Method or intended Work; neither the reference nor the description is enacted.
    3. CC‑A.2.9‑3 (Recognition taxonomy and scheme). The actual occurrence satisfies at least one SpeechActTypeRef defined by the exact recognition-taxonomy episteme under the stated effective reference scheme. Merely writing a token into SpeechActRecord.actTypes is insufficient.
    4. CC‑A.2.9‑4 (Actual extent versus effect interval). The occurrence has an actual temporal extent, and a record's window truthfully states it at the required precision. Every instituted relation keeps its own occurrence or validity interval; neither interval creates or absorbs the other.
    5. CC‑A.2.9‑5 (Observable relied-on occurrence). If a checklist, guard, commitment, or grant cites the occurrence, one SpeechActRecord identifies it and cites an applicable utterance, carrier, or direct evidence relation. Evidence-critical uses SHOULD cite at least one carrier through A.10.
    6. CC‑A.2.9‑6 (Current policy and typed world-side effects). A record's institutes.* branch references only an exact commitment or obtaining relation occurrence through its declared RefKind. The exact current policy or procedure and direct owner establish any institutional effect; a status claim and its evidence stay separate, and no record field makes an effect obtain.
    7. CC‑A.2.9‑7 (F.9 only for actual cross-locality dependence). A receiving claim cites an F.9 Bridge only when it really compares, substitutes, or transfers speech-act or policy meaning across different local taxonomies, schemes, or policies. A new consumer or locality label alone neither requires a Bridge nor transfers force.
    8. CC‑A.2.9‑8 (No fabricated method anchor). If the occurrence's actual enactsMethod -> U.Method relation cannot be recovered, the record names the unresolved claim and source-gap provenance, remains observationOnly, and is not used for gate or deontic provenance. A placeholder U.MethodDescription never closes the gap.
    9. CC‑A.2.9‑9 (Subject, target, and effect stay distinct). A record uses utteranceSubjectRefs for aboutness and institutionalTargetRefs only for a policy-selected target. It claims actual change or institutional effect only through the exact direct relation; an informative act needs no changed target.
    10. CC‑A.2.9‑10 (Optional channel stays separate). A channelRef, utterance description, carrier, or trace may support identification or observation but is not the speech act, Method, performer, assignment, or instituted effect.

    Last Updated: 2026-08-01 — upstream FPF commit 9a9a42e4 (github.com/ailev/FPF)