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:6531

    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. SA-Publish-API-v12 is the actual occurrence; the record is a separate episteme about it.

    • Actual occurrence: SA-Publish-API-v12 : U.SpeechAct

    • SA-Publish-API-v12-Record : SpeechActRecord

      • speechActOccurrenceRef = SpeechActRef(SA-Publish-API-v12)
      • actTypes = {SpeechActTypeRef(Publish@APISpecContext), SpeechActTypeRef(DeclareNorms@APISpecContext)}
      • performedBy = U.EntityRef(StandardsEditor_A) where StandardsEditor_A : U.System
      • performedUnderAssignment = RoleAssignmentRef(StandardsEditor_A@PublisherRole@APISpecContext)
      • enactsMethodRef = U.EntityRef(SpecPublicationMethod_v12); the actual enactsMethod relation independently obtains
      • methodDescriptionRef = EpistemeRef(SpecReleaseProcedure_v12)
      • reliancePosture = relianceReady
      • executedWithin = SpecPublicationSystem
      • window = [t,t]
      • judgementContextRef = APISpecContext
      • utteranceSubjectRefs = {EpistemeRef(APISpec_v12)}
      • institutionalTargetRefs = {EpistemeRef(APISpec_v12)}
      • utteranceRefs = {EpistemeRef(APISpec_v12)}
      • carrierRefs = {CarrierRef(GitTag:v12), CarrierRef(SignedReleaseArtifact:v12)}
      • institutes.publicationRelations = {EpistemePublicationRelationRef(APISpec-v12-Publication)}

    • APISpec-v12-Publication : EpistemePublicationRelation separately names the selected APISpec_v12 edition, audience declaration, bounded-use declaration, publication form, and exact carrier; it obtains only while that edition is available under E.24.PUB.

    The same APISpec_v12 episteme is both the subject of the publication utterance and the object made available by the publication relation, but those are different relations. The act does not thereby change the spec's claim content or make the episteme an actor. If D-StdStatus-APISpec_v12-Published is needed, keep it as a separate C.2.1 claim about the publication occurrence and cite its evidence through A.10; do not put the claim in institutes. Norms live in the published utterance descriptions, while the act of publication is performed by StandardsEditor_A under its publisher assignment.

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