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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:10:20 UTC

E.24.PUB:4.1 - Identify the publication occurrence

EpistemePublicationRelation is the direct relation kind whose occurrence makes one selected episteme edition available to a declared audience for a declared bounded use.

Its actual participants are:

Participant meaningAdmitted valueWhat the value supplies
selected episteme editionone exact U.Episteme identified under C.2.1the claims made available
audience declarationone U.Episteme whose claims identify the intended receiving entities or a C.3-governed local kind and its membership criterionwho is included; a reader label alone is insufficient when the boundary matters
bounded-use declarationone U.Episteme whose claims state the operations or decisions supported, the conditions of that use, and the excluded stronger usewhat availability is for; actual reliance remains another relation
publication formone exact U.Entity used as the selected arrangement, notation, or rendering convention that expresses the edition for the bounded usehow the edition is expressed; visible shape alone does not establish this use
presentation carrierone exact U.PresentationCarrierwhat physically or digitally bears the selected form

The use of common U.Entity for the publication-form participant does not admit a universal publication-form U-kind. Publication form is a relation-defined participant meaning here: the exact entity keeps the more specific kind and identity supplied by its direct pattern, and it fills PublicationFormSlot only while PublicationFormExpressionRelation obtains for the selected edition and bounded use. This is one predicate over a real common kind, not a prose union of cards, tables, diagrams, and files. E.8 governs FPF pattern form; E.17 governs multi-view publication forms and faces; a domain publication pattern may govern another form.

The reusable declaration is:

EpistemePublicationRelationSignature:
  RelationKind: EpistemePublicationRelation
  SlotSpecs:
    SelectedEpistemeEditionSlot: ValueKind=U.Episteme, refMode=U.EpistemeRef, Required
    AudienceDeclarationSlot: ValueKind=U.Episteme, refMode=U.EpistemeRef, Required
    BoundedUseDeclarationSlot: ValueKind=U.Episteme, refMode=U.EpistemeRef, Required
    PublicationFormSlot: ValueKind=U.Entity, refMode=U.EntityRef, Required
    PresentationCarrierSlot: ValueKind=U.PresentationCarrier, refMode=U.EntityRef, Required

These SlotKinds name participant meanings only inside this RelationSignature. They do not create five new U-kinds, and a card field with a similar label does not become one of these SlotSpecs.

The audience-declaration episteme identifies the audience criterion; it is not the audience and does not prove access by any particular system. A concrete system’s access, reading, reliance, or later work is another direct relation or work occurrence. This lets one publication be available to every entity satisfying a stable criterion without inventing U.Audience or treating a changing set of readers as changing participants of the same publication occurrence.

EpistemePublicationRelation obtains while all of the following are true:

  1. PublicationFormExpressionRelation relates the selected edition, publication form, and bounded-use declaration;
  2. PublicationFormBearingRelation relates the exact carrier and publication form;
  3. entities admitted by the audience declaration can obtain the expressed edition from that carrier under the conditions stated by the bounded-use declaration;
  4. the selected edition, declarations, form, and carrier remain the identified participants of this occurrence.

One occurrence is reidentified by those five fixed participants and their maximal continuous interval of availability. Changing any participant yields another publication occurrence. Demonstrated loss of availability followed by restoration yields a later occurrence. Missing or stale evidence leaves current obtaining unresolved; it does not prove a gap.

Rendering, printing, uploading, indexing, or granting access are activities separate from the publication occurrence. If one is independently claimed as dated Work, apply its direct Work and attribution patterns; E.24.PUB does not restate their admission, assignment, or compact-reporting rules. The activity and any result remain separate from the publication-relation participants.