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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 19:05:20 UTC

A.16.0:4.1 - Keep the account positions distinct

Keep the account’s own identity and publication distinct from these seven values described in its history:

  • selected episteme edition - the current U.Episteme whose claims are being positioned or re-expressed;
  • lineage links - independently established derivation, supersession, fork, merge or retirement relations among the selected epistemes, each under its defining predicate; state a no-successor result when that is the supported account;
  • grounds or witnesses - disturbances, discrepancies, traces, model outputs, bodily tensions, contrasts, or exemplars that justify the history;
  • publication form - a cue pack, routed cue set, prompt form, typed route-bounded projection form, partial normal form, or endpoint-bound record used to express an edition;
  • publication occurrence - an EpistemePublicationRelation occurrence only when availability to an audience for a bounded use matters;
  • publication face - the MVPK face on which a form is rendered when face typing matters;
  • carrier - the document, console note, card, trace file, model output, or other entity that bears the form.

A form, face, carrier, or publication-occurrence change can leave the selected episteme unchanged. A changed C.2.1 discriminator identifies another episteme. Call it a continuing edition only when the exact C.2.1 EpistemeEditionRelation obtains; any other lineage claim requires its own defining predicate and obtaining facts. Publication alone creates neither the episteme nor a lineage link.

Several live routes for one selected edition are not yet a lineage fork. A fork claim requires independently identified successor epistemes and the obtaining lineage predicate under its direct rule. Disclose losses and any authority facts that the selected account or that rule actually needs; authority is not a universal extra fork participant. Publication of the successors is not a universal prerequisite, and two publications of the same edition create no fork.

A trajectory step may reuse one edition in another form, add a successor episteme, or relate several epistemes through fork, merge, supersession, or retirement. It does not describe a trajectory of the source phenomenon.

Here route names an A.16 move-family label or a typed upstream publication-form cue. It is not an action route, work sequence, workflow, or transformation-flow path.