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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:50:10 UTC

E.10:8.3 - Prefix discipline

M-P1 (Reserved prefixes). U. is reserved for admitted U-kinds and dependent U.* forms admitted under their definitions; Γ_ for algebraic operators; CAL, LOG, and CHR for pattern packages. A local glossary, scheme, source label, or use never mints U.*.

M-P2 (Edition and version markers). Use a model-use marker only when A.1.1’s direct model-use relations or a selected BoundedModelUseStructure require it. Select one exact episteme edition only through a typed reference whose referent is that exact U.Episteme, with a narrow selector defined at its reference-pattern locator. Do not attach an edition selector to an EntityOfConcern-side Method, Space, system, bare Service, or their references. When a use depends on a defining, describing, CG-Spec, service-description, or service-offer episteme, reference that episteme separately. A service-access publication, publication occurrence, publication form, and carrier retain their own references and do not inherit the episteme selector. Tool and carrier versions remain separate. Authors may annotate local service labels for didactics only after every named value is recoverable. Norms (edition, release, and version).

  1. edition — one exact U.Episteme with its own C.2.1 identity. A later episteme is related to an earlier one only when the exact EpistemeEditionRelation predicate obtains; shared label, order, file version, or selector value establishes none. PhaseOf may describe one unchanged episteme over a proper interval but never connects different episteme identities.
  2. release — a separately governed publication or release occurrence, or the exact Work that performs it when that Work claim is current. Publication occurrence, publication form, and carrier remain distinct; release establishes neither episteme identity nor EpistemeEditionRelation.
  3. version — a tooling or carrier identifier for a file, package, code object, rendering, or other carrier-specific use. It is not an episteme edition, publication occurrence, or release claim and does not belong in Core EntityOfConcern names.

Property discipline. There is no universal <Thing>Ref.edition property. A direct reference pattern may define a narrow edition selector only for a governed reference whose referent is one exact U.Episteme. A Space, U.Method, formula, system, publication form, or carrier reference remains a reference to that object; pair it with a separately governed episteme reference when one exact defining or describing edition matters. A selector value identifies neither an edition relation nor historical continuity.