fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 94966–94980

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:30:19 UTC

E.17:5.1 - Terminology (normative)

  • View (U.View): the same C.2.1 episteme individual for which EpistemeViewpointConformanceRelation(E,P) obtains under E.17.0 for an exact U.Viewpoint episteme P. A publication-form label, viewpointRef, direct authoring, A.6.3 construction, or publication occurrence does not establish that membership. An ordinary publication form exposes its current source reference and separate reader/use declaration; add the exact publicationViewpointRef, conformance relation, scope, occurrence, carrier, or pins only when those identities change publication or reliance.
  • Publication vs expression vs bearing vs presentation vs rendering vs representation (guard):
    • Publication occurrence = the E.24.PUB EpistemePublicationRelation among the selected episteme edition, audience declaration, bounded-use declaration, publication form, and U.PresentationCarrier. Ontically these participants stay distinct; spell out their exact identities when availability, recurrence, dispute, cross-context exchange, or reliance depends on them. Preparing or inspecting an ordinary face need not begin with a five-participant dossier. A.6.3 construction and E.17.0 conformance remain separate.
    • Form expression = PublicationFormExpressionRelation among the selected edition, exact publication form, and bounded-use declaration. It states that the form expresses enough of that edition for the use; omission, coarsening, or changed admitted operations can end it without changing the carrier.
    • Carrier bearing = PublicationFormBearingRelation between the exact U.PresentationCarrier and exact publication form. It states that this carrier bears the recoverable form; it is neither publication availability nor episteme identity.
    • Presentation = rhetorical arrangement of a published carrier; notation-neutral, adds no claims and is not a publication-face kind.
    • Rendering = display layout of a carrier, purely graphical formatting; performed rendering is separate U.Work on its exact carrier, not a publication-face kind or publication occurrence.
    • Representation = a C.29 representation and its exact correspondence to independently recovered objects or relations; it is not a publication occurrence, publication form, view-membership rule, or carrier. Publication or representation does not by itself make any represented object or relation exist.
  • Architecture-description mapping note. An architecture viewpoint maps to one exact U.Viewpoint episteme; PublicationVPId or EngineeringVPId designates it and a U.ViewpointRef resolves it. An architecture view maps to one exact episteme that passes E.17.0 conformance. An MVPK face is the separate publication form through which that episteme may be exposed for a separately declared bounded use and, when material, in an exact publication occurrence.
  • Publication work: Build, rendering, upload, or delivery may be actual U.Work performed by an exact System recovered through A.13. When such Work is current, A.15.1 independently identifies the Work, performers, Method, time, and containing System. Add F.6 only when the publication account expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; missing or failed F.6 leaves the Work intact. Name a carrier relation separately only when the claim or downstream use depends on it.
  • Viewpoint (U.Viewpoint) - an exact claim-bearing episteme edition recognized under E.17.0’s dependent-kind rule. Resolve an existing viewpoint when it already states the relevant concerns and conformance rules. Author a new reusable viewpoint, or create an E.17.1 local family declaration inside an exact catalogue episteme edition, only when the current reader/use cannot be served truthfully without that separate result. The declaration packages exact U.ViewpointRef values; it is not another bundle entity. PublicationVPId designates the viewpoint episteme; U.ViewpointRef resolves it.
  • Explanation-use profile values. An existing publication form can be paired with a bounded explanation-use profile value such as SourcePinnedExplanation, SourceLinkedExplanationReconstruction, DidacticRetelling, or SpeculativeRetelling; the profile value is neither the form nor a new face, explanation, or carrier-rendering kind. Pins, provenance references, and no-new-A.6.B-boundary-claims discipline apply only when the exact source, transformation, or receiving use makes them material.