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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:55:10 UTC

E.10.D2:8.3 - Edition, publication, form, and carrier

Changed ClaimGraph, EntityOfConcern, or effective ReferenceScheme identifies another episteme under C.2.1. When the receiving use also claims continuity between two epistemes, use the exact C.2.1 edition relation. A version label, file history, publication order, shared name, or collection membership establishes neither another episteme nor edition continuity.

Use E.24.PUB to distinguish these actual publication-side objects and relations:

Current object or relationWhat it doesWhat it does not establish
selected episteme editioncarries the claim content made availablepublication occurrence, form, carrier, audience access, or reliance
audience-declaration epistemestates the audience criterionthat a concrete receiver obtained, read, understood, or relied on the edition
bounded-use-declaration epistemestates supported operations or decisions, conditions, and excluded stronger usespermission, acceptance, assurance, or actual work by itself
publication formexpresses the selected edition for the declared publication useepisteme identity or a durable public form kind by position
U.PresentationCarrierphysically or digitally bears the publication formthe episteme, the form, or the EntityOfConcern
publication occurrencemakes the selected edition available to the declared audience for the declared bounded useexpression, bearing, access work, reading, or reliance

The subject pattern keeps the verbs exact: PublicationFormExpressionRelation relates edition, form, and bounded-use declaration; PublicationFormBearingRelation relates form and carrier; EpistemePublicationRelation governs bounded availability of the selected edition through that form and carrier. Rendering, printing, uploading, indexing, or access-control work remains dated U.Work performed by systems. Plain “published episteme” names contingent participation in a publication occurrence, not a durable U.EpistemePublication kind.

One encountered thing can enter several relations without their objects collapsing. A completed inspection card may be a claim-bearing episteme; its reusable layout may be a publication form; a sheet or file may be a carrier; and a publication occurrence may make the selected card-episteme edition available to a maintenance team for one bounded use. Each claim is recovered independently.