FPF Reference

    A.2.9:5.3 — Show #2 (episteme archetype: publishing a spec edition without making the spec an agent)

    Preface node heading:a-2-9-5-3-show-2-episteme-archetype-publishing-a-spec-edition-without-making-the-spec-an-agent:5601

    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

    Situation (anti-pattern): “The interface spec declares MUST/SHALL requirements.”

    Conformant modeling sketch:

    • U.SpeechAct SA-Publish-API-v12

      • actTypes = {SpeechActTypeRef(Publish@APISpecContext), SpeechActTypeRef(DeclareNorms@APISpecContext)}
      • performedBy = RoleAssignmentRef(StandardsEditor as PublisherRole@APISpecContext)
      • isExecutionOf = MethodDescriptionRef(SpecReleaseProcedure_v12)
      • executedWithin = SpecPublicationSystem
      • window = [t,t]
      • affected = {EpistemeRef(APISpec_v12)}
      • utteranceRefs = {EpistemeRef(APISpec_v12)}
      • carrierRefs = {CarrierRef(GitTag:v12), CarrierRef(SignedReleaseArtifact:v12)}
      • institutes.statusClaims = {ClaimIdRef(D-StdStatus-APISpec_v12-Published)} (if modeled)

    Norms live in the published utterance surfaces (spec clauses as L/A/D/E-classified claims), but the act of publication is a speech act performed by an accountable role. This avoids “the spec promises/commits” category errors while preserving auditability.

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