FPF Reference

    A.2.9:7 — Conformance Checklist (normative)

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

    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 covering U.RoleAssignment has that system as holder. 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 (Act-type predicate). The actual occurrence satisfies at least one context-local SpeechActTypeRef; merely writing a token into SpeechActRecord.actTypes is insufficient.
    3. CC‑A.2.9‑3 (Actual extent versus timestamp claim). The occurrence has an actual temporal extent. A record's window must truthfully state that extent at the required precision; it does not create it.
    4. CC‑A.2.9‑4 (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.
    5. CC‑A.2.9‑5 (Typed world-side effects, separate claims). A record's institutes.* branch references only an exact commitment or obtaining relation occurrence through its declared RefKind. A grant uses GrantedPermissionRelationRef@Context; publication uses EpistemePublicationRelationRef; a subject-specific status uses its direct relation type. A status claim and its evidence stay separate, and no record field makes any effect obtain.
    6. CC‑A.2.9‑6 (Bridge-only cross-context use). A receiving claim that interprets a SpeechActRef or SpeechActRecord in another bounded context cites the Bridge/policy that licenses that interpretation.
    7. CC‑A.2.9‑7 (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.
    8. CC‑A.2.9‑8 (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.

    Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)