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

    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 : U.SpeechAct is the actual occurrence. Admitted system StandardsEditor_A performs it under obtaining StandardsEditor_A_PublisherAssignment_v12; that assignment independently identifies PublisherRole, role-taxonomy episteme StandardsRoles_v12, effective scheme APISpecReferenceScheme_v12, and an extent covering the act. enactsMethod(SA-Publish-API-v12, SpecPublicationMethod_v12) independently obtains; SpecReleaseProcedure_v12 is only a separate description of that exact Method.

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

    • speechActOccurrenceRef = SpeechActRef(SA-Publish-API-v12);
    • performedBy = U.EntityRef(StandardsEditor_A) and performedUnderAssignment = RoleAssignmentRef(StandardsEditor_A_PublisherAssignment_v12);
    • enactsMethodRef = U.EntityRef(SpecPublicationMethod_v12) and methodDescriptionRef = EpistemeRef(SpecReleaseProcedure_v12);
    • recognitionTaxonomyRef = EpistemeRef(APISpecSpeechActTaxonomy_v12) and effectiveReferenceScheme = APISpecReferenceScheme_v12;
    • policyOrProcedureRef = EpistemeRef(APISpecPublicationPolicy_v12) and optional channelRef = U.EntityRef(StandardsReleaseChannel);
    • actTypes = {SpeechActTypeRef(Publish), SpeechActTypeRef(DeclareNorms)} under that taxonomy and scheme;
    • reliancePosture = relianceReady, executedWithin = SpecPublicationSystem, and window = [2026-06-14T09:00Z, 2026-06-14T09:06Z];
    • utteranceSubjectRefs = {EpistemeRef(APISpec_v12)}, institutionalTargetRefs = {EpistemeRef(APISpec_v12)}, utteranceRefs = {EpistemeRef(APISpec_v12)}, and 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, exact carrier, availability interval and governing publication conditions under E.24.PUB. It obtains only while that exact edition remains available under those conditions. Its interval need not equal the six-minute publishing act. The same episteme can be both utterance subject and publication object without those relations becoming identical.

    The act does not 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 exact publication relation and cite its evidence through A.10; do not put the claim in institutes. Norms live in the published utterance description, while StandardsEditor_A performs the publishing Work. Another audience or scheme needs F.9 only when a receiving use actually translates or substitutes the local act or policy meaning.

    Bounded non-use. If the only question is what APISpec_v12 says, stop at A.7/C.2/E.17. If the question is whether it is available to an audience, use E.24.PUB. If the question is evidentiary support for a status claim, use A.10. Keep A.2.9 only when the actual communicative Work occurrence itself matters.

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