A.15.PROD:4.10 - Pattern NameCard
This NameCard names the recovery pattern, not a relation kind. It uses F.18’s expanded identity-bearing form with a direct local-sense claim because no separately recoverable F.17 SenseCell is current for this local naming settlement:
NameCard:
NameCardId: NC-A15-PROD-PATTERN
GovernedValueRef: the A.15.PROD pattern that separates and recovers production-work participation, entity-identity inception, and production-completion claims
SubjectPatternLocator: A.15.PROD
ReferenceScheme: FPFCoreReferenceScheme
ClaimContent: NC-A15-PROD-PATTERN.ClaimGraph — complete C.2.1 U.ClaimGraph constituted by all identity-bearing naming-settlement claims designated below
LocalSenseRef: local expression `Production Work, Entity-Identity Inception, and Production Completion Recovery`; sense claim: the A.15.PROD recovery pattern asks which of the three production questions is current while keeping actual work, first existence, completion, delivery, acceptance, release, publication, and availability distinct under FPFCoreReferenceScheme
TechLabel: Production Work, Entity-Identity Inception, and Production Completion Recovery
PlainLabel: separate production work, when this exact entity first exists, and when production was completed
CandidateSet: Production Work, Entity-Identity Inception, and Production Completion Recovery; Entity Production by Work; Entity-Identity Inception Through Work; Production Boundary Recovery
CandidateCoverage: recovery-pattern, entity-production, entity-inception, and boundary-recovery head families; no plausible current family remains untested
RejectedCandidates:
Entity Production by Work: hides whether the claim concerns work participation, first existence of the entity, or completed production
Entity-Identity Inception Through Work: omits production work before and after first existence and omits production completion
Production Boundary Recovery: uses a generic boundary head and does not expose the three governed questions
SelectionRationale: the selected title names the three distinctions that the pattern must recover and makes the completion kind explicit; it cannot be parsed as one binary or ternary production relation
LineageEntries: initial durable settlement; the selected Tech and Plain labels are current; this card asserts no alias, rename, split, merge, or retirement
RefreshCondition: reopen naming if repeated subject use justifies an admitted derived relation kind or one question needs a separate primary EntityOfConcern and recovery algorithm