E.24:5.7 - Rationale

FPF needs a pattern for ontic introduction because many important ontology units require one exact identity rule and several direct relation patterns to remain coherent. The repair is not to make one record-shaped episteme or universal head relation stand in for every nearby object. It is to give the ontic stable identity, state the smallest independently governed relation set needed by dependent use, single out an identity-bearing relation only when the subject’s subject pattern does, and add RelationSignature declarations only where dependent uses need them.

U.Episteme is the main stress case. C.2.1 identifies one episteme through claim content, exact EntityOfConcern, and effective reference scheme, while separate direct relations govern grounding and edition continuity. A RelationSignature declares reusable participant typing only when another use needs it. If a card is current, classify its actual use through E.24:4.3a; neither its layout nor its publication makes the episteme’s claims true.

A bare role cue is a second stress case because it can hide four different objects: a world-side participant, a local system-role kind and its classification judgment, an assignment occurrence, or a reusable declaration’s local participant meaning. E.10.ROLE recovers the intended use; the participant stays under its direct subject pattern, A.2 and C.3.2 govern the local kind and classification, A.2.1 governs the exact assignment species and occurrence, A.6.5 governs the declaration, and F.6 governs any current Work attribution. E.24 asks only whether the ontic decision has confused those objects or invented a common head. Their participants, predicates, obtaining and occurrence identity remain with the cited patterns. Without E.24, FPF ontology development oscillates between two bad moves. One move invents a new umbrella name and leaves the mixed ontology intact. The other refuses the new name but still leaves several patterns carrying duplicated local slot doctrine. E.24 gives a bounded ontology decision: use an existing subject pattern, introduce a durable ontic, state only the needed claims in a bounded local episteme under C.2.1, or stop unresolved. A separate source-use status preserves or strengthens the source relation without replacing that ontology decision.

E.24’s rule content and practical guidance concern the introduction decision. They do not define every ontic or become a registry of systems, epistemes, methods, mechanisms, architectures, sources, qualities, times, dynamics, or changes. If an E.24 episteme qualifies as a U.MethodDescription, A.3.1 and A.3.2 must identify the Method it describes and show substantive guidance for doing it; that gives no other pattern episteme the same membership. Each accepted subject still needs its own defining or constraining ClaimGraph; a bounded local episteme may contain claims for one declared use but does not define the ontology.