FPF Reference

    A.2.9:4.4 — Separation rules with U.Commitment, GrantedPermissionRelation@Context, and U.PromiseContent (normative)

    Preface node heading:a-2-9-4-4-separation-rules-with-u-commitment-grantedpermissionrelation-context-and-u-promisecontent-normative:6453

    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. Speech act is not the enduring deontic relation. A speech-act occurrence may institute a U.Commitment for an obligation, recommendation-as-duty, or prohibition, or a GrantedPermissionRelation@Context for strong permission. The enduring relation is the separately governed object, not the act. Do not encode obligations or permissions as prose inside its SpeechActRecord: cite commitments in institutes.commitments and grants in institutes.permissions, each under the exact instituting policy (A.2.8, A.2.8.PER).

    2. Speech act is not the service promise clause. U.PromiseContent is the promised-outcome statement; a speech act may be the act of offering or issuing that promise, but the promise content lives in the promise-content object and is referenced from the resulting commitments.

    3. Speech act is not the carrier. A “signed approval PDF”, ticket, message, or API log is a carrier; it may carry an utterance-description episteme or a SpeechActRecord. The speech act is the Work occurrence described or evidenced, not either episteme and not the carrier.

    4. Publishing a spec is not a commitment by default. Default interpretation rule (normative). A conformant model/interpreter MUST NOT infer a U.Commitment, GrantedPermissionRelation@Context, publication occurrence, or subject-specific status relation solely from a Publish/Approve speech-act occurrence or its record. Publication work may establish an EpistemePublicationRelation only when E.24.PUB's selected edition, audience, bounded use, form, carrier, and availability conditions obtain. A constitutive policy may let an act institute a subject-specific Approved, Published, or similar status relation; then cite that exact relation occurrence through the subject pattern and separately cite any C.2.1 status claim and A.10 evidence. The claim represents the status; neither its ID nor its publication makes the status obtain.

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