A.15.PROD:4.5 - Recover entity-identity inception

Definition: A15PROD-D1 (Entity-identity inception). Entity-identity inception is the boundary at which exact producedEntity first satisfies the identity rule stated by exact productIdentitySpecification and a named applicability predicate or filled local claim applies that specification to the candidate basis, subject context, and boundary. Plain: when this exact entity first exists. inceptionBoundary is a case-local boundary designator, not a second technical term, claim kind, or relation kind.

For this branch, the practitioner MUST complete all five steps:

1. recover exact productIdentitySpecification as one C.2.1 predicate-definition episteme in the subject pattern that states the identity rule. Before inception, the governed question remains about exact work, method, actual effects, that specification episteme, and its candidate basis; no future producedEntity participant exists;
2. recover the named applicability predicate or filled local claim that applies that specification episteme to the exact candidate basis, subject context, and candidate inceptionBoundary, together with the exact actual effects of exact work and the declared links by which those effects bear on that rule;
3. find the earliest exact inceptionBoundary at which the rule in that applicable specification episteme becomes true and designate the resulting exact producedEntity only on the after-side of that boundary; the pre-inception candidate basis remains distinct from that entity;
4. identify exact identityClosingWork, using the one closing work occurrence when it exists or, for jointly necessary concurrent or nested work parts, their exact composite work under A.15.1 and its declared work-part relations; and
5. constitute a positive local inception claim as one C.2.1 episteme only after exact producedEntity exists and the claim names exact productIdentitySpecification, its named applicability predicate or filled local claim, exact identityClosingWork, exact inceptionBoundary, and all declared Work-to-change and change-to-identity predicates or compound bases. Add an E.24.PUB occurrence only when a receiving use also needs that episteme to be available through a named form or carrier.

A local inception claim MUST be indexed by the exact specification episteme and applicability basis used at inceptionBoundary. A later specification episteme does not silently rewrite that earlier claim. If an exact C.2.1 EpistemeEditionRelation connects the two specifications, the lineage can trigger refresh of a current dependent use, but the later specification still needs its own applicability basis at the boundary being judged. Without that relation, treat the later object as a non-continuing replacement and evaluate it independently. Changed applicability yields either a separately qualified claim under its new exact basis or an exact blocker; it does not move the earlier indexed boundary.

Supporting material, whether a representation, plan, record, rule episteme, or observation, enters one of the five steps only through its declared relation to that step; it does not replace the required Work, applicability, effect, or boundary predicate. Absence of recoverable work granularity for identityClosingWork yields a work-granularity blocker. Several incomparable minimal work composites yield several local inception claims and remain plural unless a separate selection rule applies.

Regulated-identification boundary. A persistent identifier is not an inception criterion. A current subject practice that allocates an identifier at build or registration while keeping allocation separate from entity status supplies designation and continuity only. First existence requires a separately applicable subject-identity rule; its absence yields the exact identity-governor blocker. An assigned number does not make the candidate basis the after-side entity.