Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:25:20 UTC

A.2.9:5.3 - Show #2 (episteme archetype: publishing a spec edition)

Situation: “The interface spec declares MUST/SHALL requirements.” This sentence describes the specification’s contents. The current task is to model publication of version 12 and determine its institutional effects.

Conformant modeling sketch. SA-Publish-API-v12 : U.SpeechAct is the act. PublisherSystemRole is an exact local agential system-role kind whose criterion for this use is the capacity to execute the policy-recognized publication act; StandardsEditor_A is classified under it for this scope and window, and evidence supports that core classification without a Grade or autonomy-profile claim. StandardsPublicationAssignment is a declared U.SystemRoleAssignment species. Under A.2.1 it declares the ordered holder and assigned-kind positions, their domains U.System and PublisherSystemRoleKindDomain, its direct predicate and applicability, and its occurrence-identity rule. Occurrence StandardsEditor_A_PublisherAssignment_v12 obtains with admitted System StandardsEditor_A as holder, PublisherSystemRole as assigned-kind value, and an extent covering the act; it is the same assignment used by A.13 and F.6. StandardsEditor_A performs the act under that assignment. Taxonomy StandardsSystemRoles_v12 and APISpecReferenceScheme_v12 interpret the assertion but are not assignment participants. The Work enacts Method SpecPublicationMethod_v12; SpecReleaseProcedure_v12 is only a separate description of that Method.

SpecPublicationWorkBoundaryRelations declares PublicationWorkOccursWithinSpecSystemBoundary(work, system) for the publication-system delimitation and act window; occurrence PublicationWorkWithinSpecSystemBoundary-v12 obtains for SA-Publish-API-v12 and SpecPublicationSystem. SA-Publish-API-v12-Record : SpeechActRecord states:

  • speechActOccurrenceRef = SpeechActRef(SA-Publish-API-v12);
  • actualPerformerSystemRef = U.EntityRef(StandardsEditor_A) and performedUnderAssignmentRef = U.RelationRef(PerformedUnderPublisherAssignment-v12), resolving to the F.6 relation between the act and 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, workContainmentRelationRefs = {U.RelationRef(PublicationWorkWithinSpecSystemBoundary-v12)}, and window = [2026-06-14T09:00Z, 2026-06-14T09:06Z];
  • utteranceSubjectRefs = {EpistemeRef(APISpec_v12)}, institutionalTargetRefs = {EpistemeRef(APISpec_v12)}, utteranceDescriptionLocators = {U.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.

Publication makes the selected APISpec_v12 edition available with its claim content unchanged. 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.