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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:50:10 UTC

A.16:4.3 - Decide identity before describing movement

Do not use “move between publication forms” as a shortcut across these three cases:

  1. First typed preservation. A precursor cue, trace, contrast, or witness may have no source episteme or source publication form. Name the precursor and the first typed preservation form. C.2.1 governs the identity of the first claim-bearing episteme when one is admitted.
  2. Same episteme edition, another form. When EntityOfConcern, ClaimGraph content, and effective reference scheme remain the same, one episteme edition may be issued in another form or on another carrier. Name the episteme and source and target forms only when they matter. E.24.PUB governs each claimed availability occurrence; neither form nor occurrence creates a successor episteme.
  3. Content-changing successor. When a C.2.1 discriminator changes, identify a separate target episteme. Name the source and target epistemes, the changed discriminator, what content is preserved, changed, and lost, and the exact lineage relation only when its predicate obtains. A repeated label, form, carrier, or move name proves no continuity. Use A.16.0 only if the multi-step or branching history is load-bearing.

The same discipline applies to project records through their own identity patterns. E.24.PUB says that an already identified episteme was made available for a bounded use; it says neither that content changed nor that an endpoint test passed.