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 07:42:37 UTC · snapshot created 2026-10-03 07:43:27 UTC · last check 2026-10-03 08:00:10 UTC

E.24:4.2 - Check 2: Stable Identity Test

A candidate qualifies as a durable ontic only when it has stable identity beyond one local wording issue, source expression, or bounded local episteme used for first explanation.

Ask:

  1. What exact candidate entity, proposal episteme, or source-construct entity is independently identifiable before judgment, and what direct rule identifies it as the fixed EntityOfConcern of the decision episteme?
  2. Which exact result payload follows from each available disposition without replacing that fixed EntityOfConcern: closing assertions, a bounded episteme, a selected ontology-unit individual, or an unresolved reason?
  3. What changes the identity of that ontic?
  4. What does not change ontic identity, even if an ontic-description episteme, publication form, notation, view, or presentation carrier changes?
  5. Which direct world-side relations and grounding conditions are required for identity?
  6. Which dependent patterns may rely on that identity? If those questions cannot be answered, keep any needed coordination in a bounded local episteme under C.2.1 or use the subject patterns without another coordination episteme.

Test the invariant against the subject before filling a relation field:

Governed subjectIdentity, constitution, or recognition ruleRelation-set consequence
Holon or SystemA.1’s exact candidate, constituents, constructive part relations and assembly, reidentification, whole-level characteristic, larger-assembly compatibility, and any kind-specific conditionkeep those facts under their subject patterns; A.1 explicitly forbids compressing them into one universal relation signature
MethodA.3.1’s semantic way-of-doing identity and any independently governed method-holarchy factsname only the direct relations needed by dependent method use; no head relation is presumed
WorkA.15.1’s dated occurrence identity and continuity ruleperformer, enacted method, affected referent, resources, and results stay under their exact direct relations or A.6.1 bindings
TransformationA.3.4’s independently identified actual bounded change at the selected resolutionwork, flow, production, representation, and receiving-use relations remain separate; no core relation is invented
EpistemeC.2.1’s constitution ruleEpistemeConstitutionRelation is identity-bearing because C.2.1 explicitly selects it; empirical grounding, edition, conformance, and publication remain neighboring relations
RelationA.6.REL plus each direct relation pattern’s obtaining and occurrence-identity rulethe ontology unit coordinates common occurrence discipline with those direct rules; no relation-to-relation head occurrence is required