#Production Work, Entity-Identity Inception, and Production Completion Recovery

A.15.PROD · Stable · Architectural (A) · Normative unless marked informative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative

Plain name. Separate production work, when this exact entity first exists, and when production was completed.

At a glance. Production wording often compresses three questions: is this dated Work the whole production Work or only a declared part; when did changes attributed to that Work first make the applicable identity rule true so this entity began to exist; and when did the actual state satisfy the applicable production-completion criterion? This pattern answers each question with a separate local compound relation-bearing claim. It introduces no universal production relation or production-work kind. Call one specification or criterion an edition of another only when their exact C.2.1 EpistemeEditionRelation obtains.

Plain claim-record gloss. A local compound relation-bearing claim is one checkable statement for one selected question, built from already governed facts. It is neither an omnibus production record nor a new relation kind. Whole production work, first existence, and completion therefore remain three separate claims even when they cite overlapping facts.

Use this when. Practitioners SHOULD use this pattern when work is said to have made, produced, built, assembled, grown, generated, finished, or completed something and the receiving decision needs to know which exact production question is true. They SHOULD prefer it when one work occurrence is nested in larger work, several work parts act concurrently, an entity becomes identifiable before all work ends, or completion is being confused with delivery, acceptance, release, publication, or availability.

#Relations

#Content

#Problem Frame

Use this when. Practitioners SHOULD use this pattern when work is said to have made, produced, built, assembled, grown, generated, finished, or completed something and the receiving decision needs to know which exact production question is true. They SHOULD prefer it when one work occurrence is nested in larger work, several work parts act concurrently, an entity becomes identifiable before all work ends, or completion is being confused with delivery, acceptance, release, publication, or availability.

Primary EntityOfConcern by selected branch. Production wording is the umbrella. Each application narrows to one exact local claim whose C.2.1 EntityOfConcern is exact currentWork for production-work participation, exact producedEntity after inception for entity-identity inception, or exact productionWork for production completion. When more than one branch is current, each branch retains its own claim episteme and EntityOfConcern; one manufactured union concern is inadmissible.

Primary working reader. A practitioner or modeler responsible for settling one of these production, identity, or completion questions for a current engineering, manufacturing, construction, lifecycle, audit, or scientific use before relying on delivery, acceptance, release, publication, or availability.

Primary viewpoint. The practitioner SHOULD recover the smallest receiver-relevant claim: select one branch, identify its exact EntityOfConcern, and stop when that branch is decided or its exact blocker is known. This pattern is not a form to fill in.

First useful move. The practitioner SHOULD first ask which answer the receiving action or decision needs now:

1. Is this dated Work the whole production Work for this use, or a declared proper part of it?
2. Which identity rule applies to the candidate, and at what boundary did changes attributed to this Work first make that rule true so this entity began to exist?
3. Which completion criterion applies to this production Work, and at what boundary did the actual state satisfy it?

The practitioner MUST NOT answer one question with evidence for another.

What goes wrong if missed. Any work-caused change is called production; an entity is treated as existing before its identity rule first holds; a finishing operation is mistaken for entity creation; a plan, log, post-state picture, or first observation is treated as the change-producing link; and later delivery or acceptance silently rewrites historical completion.

What this buys. Teams can attribute production work at the right work boundary, state when one entity first exists, and preserve historical completion without inventing a universal relation kind. Narrow and larger production readings can coexist through exact work-part relations. Identity, completion, rework, delivery, acceptance, release, publication, and availability remain independently inspectable.

Cross-domain recognition test. These three non-exhaustive recognition situations show that the same three production questions remain separate across heterogeneous practice:

So-what adoption test. Would replacing the separate branch answers by one broad production sentence change what the receiver may rely on, schedule, audit, accept, release, or reopen? If yes, the practitioner SHOULD apply this recovery. If only one already-governed neighboring claim is current, the practitioner SHOULD use its direct pattern instead.

Not this pattern when. Practitioners SHOULD use A.15.1 directly when the only question is what work occurred; A.3.4 when the only question is what actually changed; A.3.1 when the only question is the reusable way of doing; the direct identity pattern when only entity identity is current; or the direct evaluation, delivery, acceptance, release, publication, availability, evidence, or assurance pattern when only that neighboring claim is current. This pattern coordinates those objects only for a selected production-recovery question.

No-mint disposition. Authors and modelers MUST NOT introduce U.ProductionWork as a U-kind. They MUST NOT introduce WorkProducesEntityRelation, EntityIdentityInceptionByWorkRelation, ProductionWorkRelation, or ProductionCompletionRelation as universal relation kinds. The default result is one local C.2.1 claim episteme per selected question under A.6.RCD disposition 2. Repeated use of the same predicate with the same participant meanings in one subject practice may justify one reusable predicate-definition episteme in that practice's owning pattern. Consider a derived relation-kind candidate only when a named later action must refer again to the same obtaining relation occurrence rather than merely reuse the predicate; A.6.RCD and later admission govern that continuation.

#Problem

Production speech crosses several ontological boundaries. Exact dated work is an occurrence. An actual transformation is the bounded change of a referent. An identity-specification episteme states when a candidate counts as the entity in question; a named applicability predicate or a filled local claim under A.6.RCD disposition 2 must apply that episteme to the candidate basis, subject context, and boundary. Another specification episteme is a continuing edition only when an exact C.2.1 EpistemeEditionRelation obtains; a similar label, later date, or changed rule does not establish that lineage. Entity-identity inception is the first boundary at which the exact applicable specification's rule becomes true. Production completion is satisfaction of an exact applicable completion-criterion episteme by a subject state at a boundary of exact production work. A measurement or evaluation result is a separately governed value or episteme about its exact concern; it is neither the produced entity nor production completion itself.

These boundaries often differ. A ship can first exist while outfitting continues. A car can already exist before a required nut is fastened. A finished product can later be damaged, delivered, rejected, repaired, republished, or made unavailable. One broad production predicate hides those differences and also hides the exact missing governor when attribution cannot be established.

#Forces

#Solution

The practitioner MUST choose one of the three production questions, name the Work and the affected referent, candidate basis, or produced entity involved, and gather only the facts that decide that question. The practitioner MUST state each answer as a separate local compound relation-bearing claim and MUST stop or return an exact blocker when a required predicate, criterion, applicability rule, boundary fact, work granularity, or transformation-composition rule is missing. If another person, tool, or later decision must reuse the answer, publish that one claim as a C.2.1 episteme.

Core and branch cut. The common recovery core is receiver-first question selection, exact-object recovery, closure through declared predicates or one local claim selected under A.6.RCD disposition 2, and a deliberate stop. The production-work, entity-identity-inception, and production-completion branches add only their own EntityOfConcern, criterion or boundary, and branch-specific base. One branch neither inherits facts from another nor turns the common method into an omnibus production object. Work identity, transformation identity, subject identity, evidence, assurance, delivery, acceptance, release, publication, and availability remain with their governing patterns.

#Split the three questions before recovering evidence

The three claims may cite overlapping facts. They remain different claims because they answer different receiving questions and can have different boundaries, criteria, and truthful C.2.1 EntityOfConcern values.

#Recover the smallest exact base

The practitioner MUST use only objects needed by the selected branch:

A method description, work plan, objective, commitment, product specification, evaluation result, or publication enters only when a named predicate or filled local claim connects it to the selected Work, entity, or claim and omitting that connection would change the named action or decision. Otherwise keep it separate. None is constitutive of every production occurrence.

#Select one production-work branch

Whole-work branch. currentWork = productionWork is admissible only when that exact dated Work enacts productionMethod; the method states its intended production effect; a named applicability claim applies the method to this case's inputs and conditions; the named work-to-change predicates obtain for the exact Work and transformations; and the identity or completion criterion that decides the selected question is named and applicable. A familiar broader production label establishes no parent work.

Proper-part branch. Exact currentWork is admissible as a proper part of exact productionWork only when OperationalPartOf_work or another exact A.15.1 work-part relation with fitting occurrence semantics obtains. Interval overlap or concurrency is asserted separately and establishes neither parthood nor coordination. The containing Work must likewise enact the production method; the method must state its intended production effect; a named applicability claim must apply it to the containing case; the named work-to-change predicates must obtain; and the identity or completion criterion that decides the selected question must be named and applicable. A shared label, project membership, common referent, temporal containment, overlap, or adjacency in a plan establishes no work parthood.

The two branches can support different bounded uses. A nut-fastening occurrence can be the whole production work for a narrowly bounded finishing operation and also a proper part of a larger car-production occurrence, provided each local claim names its exact extent, criterion, and work relation. productionWork is a relation-defined reading of one Work occurrence admitted under U.Work, not an intrinsic kind.

#Ground actual effects without inventing transformation composition

The practitioner MUST first recover every actual transformation independently through A.3.4: changed referent, exact extent or formal boundary, boundary conditions, actual before/during/after facts, and continuity or reidentification rule. The practitioner MUST then name the declared domain predicate for each exact Work-to-transformation pair, state its participant order, and show the case facts that make it obtain. If no one direct predicate suffices, use a local compound claim selected under A.6.RCD disposition 2 only when its constructor, governed base predicates, actual participants, and case facts are recoverable. If neither route is present, keep the Work and transformation separately and return missing-governor[work-to-change]. Temporal overlap, a common changed referent, a delta expression, a log record, or a post-state picture does not establish the link.

One transformation identified at the resolution needed by the production claim establishes neither presence nor absence of finer transformation parts. Work parts, method parts, samples, temporal subdivisions, concurrent changes, and flow representations do not establish transformation parts or a composite transformation.

If the selected production claim uses only independently identified transformations, continue without a composition claim. If it asserts positive composite-transformation identity, transformation parthood, or transformation holonhood and no accepted governor supplies that basis, return the exact missing-governor blocker. Composite identityClosingWork under A.15.1 does not cure that blocker and does not imply an isomorphic composite transformation.

#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. publish a positive local inception claim 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.

A published 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.

A delta expression, method description, work plan, log, post-state image, identity-rule episteme, or first observation establishes none of those links by itself. Absence of recoverable work granularity for identityClosingWork yields a work-granularity blocker. Several incomparable minimal work composites yield several local inception claims; narrative simplicity supplies no rule for selecting only one.

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.

#Recover historically indexed production completion

A production-completion claim designates:

• exact productionWork;
• exact completionBoundary inside or at the end of that occurrence;
• exact productionCompletionCriterion episteme applicable to that occurrence at that boundary;
• the named applicability predicate or filled local claim that applies that criterion episteme to the production Work and boundary; and
• the actual boundary-state facts and the criterion predicate they satisfy at that boundary.

Completion is historical. Later damage, loss, destruction, delivery, rejection, acceptance, release, publication, or unavailability does not erase an earlier true completion claim. A later or replacement criterion episteme does not rewrite the earlier claim, whether or not an exact C.2.1 EpistemeEditionRelation connects it to the criterion used then. Rework or later production work that satisfies an applicable criterion at a later boundary receives a separate local completion claim.

Entity-identity inception and production completion remain separate claims even when they share a boundary. The identity-specification episteme says when this exact entity first exists only together with the named applicability predicate or local claim that selects its candidate basis, subject context, and boundary; the completion-criterion episteme says when the separately applicable production requirement was satisfied. A later evaluation-result episteme may support either assertion under a direct evidence-use relation, but it creates neither the boundary nor the subject state.

Past work, entity-identity inception, and production completion remain addressable after later destruction or evidence decay. A later assertion carries its own evidence currentness and reliance status. The produced entity, measurement or evaluation result, delivered entity, acceptance verdict, release, publication, availability, and downstream effect remain separately governed objects and claims.

Practice-specific completion criteria stay local. In current NASA systems-engineering practice, product implementation or integration, verification, validation, and product transition are distinct processes; a local completion claim therefore names the exact tailored product-layer criterion and does not substitute transition or delivery for verification or validation. In current Scrum practice, the applicable Definition of Done is a product-specific quality-state criterion and an Increment is born when a Product Backlog item first meets it; Sprint Review and release remain separate. These practice answers can supply an exact criterion or boundary only in their own applicability context. They supply neither the exact A.15.1 work occurrence nor a cross-domain universal completion rule.

#Publish local claims, not an omnibus relation

The default A.6.RCD disposition is local compound relation-bearing claim. For an ordinary positive answer, the practitioner MUST:

1. name the receiving action or decision, state what it must decide, and select one production question;
2. recover the exact participants, direct predicates, applicability facts, and boundary facts needed by that question;
3. state the smallest readable conjunction of those governed facts and the one answer it supports, or return the exact missing-information, missing-governor, criterion, applicability, work-granularity, or boundary-state blocker; and
4. keep any durable answer in one truthful C.2.1 episteme with exact claim content, one exact EntityOfConcern, and an effective U.ReferenceScheme, then stop without introducing a relation kind, relation signature, or relation occurrence.

This ordinary positive branch does not require the practitioner to name a substrate document, constructor, hidden-witness policy, polarity algebra, or ordered-boundary operator. It requires the governed facts and a readable answer. Open author-side semantic replay only when A.6.RCD:4.2 requires a substrate pin—nontrivial, interoperability-facing, proof-bearing, high-consequence, or reusable use—or when the current negative claim or first-satisfying-boundary claim actually depends on negation, witness, ordering, or earliest-boundary semantics.

Branch constructor semantics for the triggered replay. These are branch-local claim constructors, not a universal production algebra:

For DPF or FPF authoring and every other pin-triggering use, the responsible author or modeler MUST name the exact selected substrate and edition and replay its constructor inputs, output claim, applicability, hidden witnesses, polarity law, and temporal policy. A negative or earliest-boundary claim MUST recover the specific negation, witness, ordering, or selection semantics it consumes even when no broader replay is needed. If no current substrate supplies semantics that the claim actually requires, return the exact missing-substrate blocker. A.15.PROD supplies no fallback operator.

For an ordinary positive result, the truthful EntityOfConcern is usually exact currentWork for production-work participation, exact producedEntity for entity-identity inception, and exact productionWork for production completion. A modeler MUST split claim content that cannot truthfully concern one exact entity and MUST NOT manufacture a union concern from work, method, transformations, criteria, evidence, and receivers.

Repeated use within one subject practice may justify one predicate-definition episteme in the pattern that owns those participant meanings. Consider a subject-specific derived relation kind only when a named later action must also refer again to the same obtaining relation occurrence. The subject definition must then state obtaining, applicability, base dependencies, recurrence, and occurrence identity. A.6.RCD governs that continuation; A.15.PROD admits no such kind by itself.

#Separate recognition from assurance

Recognition branch for ordinary work. The practitioner SHOULD ask only three questions:

1. Which is current: did this Work count as production work, when did this exact entity first exist, or when was production completed?
2. What happened, to which existing referent or pre-inception candidate basis, and at what boundary? If first existence is current, which entity exists only after that boundary? Name only the Work or work part, method, transformations, identity rule or completion criterion, declared predicates, applicability, and boundary facts needed to decide that question.
3. What one readable answer do those facts support, and what should the receiver do next? If one deciding fact or governor is absent, return its exact blocker instead of opening the other production questions.

A positive local answer can stop at that readable conjunction. It does not require substrate vocabulary. Open only the specific semantic replay needed when the answer is negative, when first existence requires an ordered earliest-boundary judgment, or when A.6.RCD:4.2 triggers a substrate pin. The practitioner MUST stop when the local answer is readable and grounded and MUST NOT fill the rest of this pattern as a record.

Assurance branch for authors and high-consequence use. Authors and high-consequence users MUST additionally replay the exact work identity and part relations; the actual enactsMethod relation; method applicability and intended production effect; every work-to-change and change-to-identity predicate; every criterion-applicability and boundary-state satisfaction fact; the exact identity-specification and completion-criterion epistemes; the named applicability predicate or filled local claim for each episteme at its claimed boundary; any separately current C.2.1 EpistemeEditionRelation; positive and discriminating cases; C.2.1 identity; evidence-use relations; and the explicit transformation-composition non-inference. DPF and FPF authors MUST record the selected substrate and edition when A.6.RCD:4.2 requires a pin, and MUST expose direct base predicates, applicability, hidden participants, polarity law, boundary domain and ordering, witness policy, and any earliest-boundary rule used by the claim. Assurance may warrant reliance on the claim; it does not constitute work, change, entity inception, or completion.

Assurance scope by use. A modeler whose declaration or model carries one local claim MUST check exact claim content, one truthful EntityOfConcern, reference scheme, participants, declared predicates, polarity, and boundary indexing. A practitioner or conformance reviewer MUST verify that the three-question first move reaches either one grounded local answer or one exact blocker and then stops. A pattern author or reviewer MUST also replay the worked and discriminating cases, neighbor-authority boundaries, checklist, and no-mint disposition. None of these assurance uses widens the recognition claim or adds a world-side production fact.

#Run the recovery sequence and stop deliberately

Ordinary sequence. The practitioner MUST stop at the first grounded answer or exact blocker:

1. name the receiving action or decision and select one production question; if several are current, handle them one at a time as separate claims;
2. recover only the exact Work, work-part, method, affected-referent, transformation, identity-specification or completion-criterion, applicability, and boundary facts needed by the selected question;
3. select the whole-work or proper-part branch when production-work participation is current;
4. state one readable conjunction and its positive answer, or return the exact blocker naming the missing fact, governor, applicability basis, criterion, work granularity, or boundary state; and
5. if another person, tool, or later decision must reuse the answer, publish it as one local C.2.1 claim episteme; otherwise keep the readable answer local, then stop. Open delivery, acceptance, release, publication, availability, result, evidence, assurance, or relation-kind questions only when the named action or decision asks one of them; none follows from the production answer.

Triggered author replay. Continue beyond the ordinary sequence only for an A.6.RCD:4.2 pin-triggering use or when a negative or earliest-boundary answer consumes additional semantics:

6. name the branch-local constructor and, when a pin is required, the exact substrate and edition; expose only the constructor inputs, applicability, hidden-participant or witness policy, polarity law, boundary domain and ordering, and temporal rule that can change this answer;
7. for entity inception, verify the ordered candidate-boundary domain and earliest-satisfying rule; for a negative claim, verify the applicable negation law; for completion, keep the claim indexed by its criterion, applicability basis, and boundary;
8. if one required operator or substrate is unavailable, return the exact missing-substrate blocker rather than lowering the absence to a negative production answer; and
9. stop after the author replay returns the same ordinary answer or blocker.

#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
  GoverningPatternRef: 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

#Archetypal Grounding

#Car 42 and the required nut

In this case, Car 42 already satisfies its identity rule before NutFasteningWork-42. A.3.4 identifies Car42FastenerAttachmentTransformation, the change in the fastener, torque, and attachment facts that occurred during the dated fastening Work. That transformation concerns the same continuing car; it does not bring Car 42 into existence.

For a narrowly bounded finishing use, NutFasteningWork-42 can be the whole productionWork when its fastening method is applicable, case-local predicate FasteningWorkChangedAttachment@Car42(work, transformation) obtains for that Work and Car42FastenerAttachmentTransformation, and the completion-criterion episteme applies at the fastening boundary. For the broader factory use, the same occurrence can be a proper operational part of CarProductionWork-42 under an exact A.15.1 part relation. First satisfaction of the applicable completion criterion at the fastening boundary yields a local completion claim; prior completion instead classifies the Work as later rework, repair, or maintenance. The verb fasten and the presence of a car decide none of these claims.

Cold-practitioner replay. Ask only whether NutFasteningWork-42 completed the narrowly bounded finishing work. In this fixture the fastening Work occurred under the applicable method, the method was meant to make the required attachment, FasteningWorkChangedAttachment@Car42(NutFasteningWork-42, Car42FastenerAttachmentTransformation) obtains, and the car satisfied the finishing criterion at the fastening boundary. The readable answer is: this Work completed the required fastening for this finishing use at that boundary; it did not bring Car 42 into existence. If the fixture instead supplies only a torque result and temporal overlap but no declaration or obtaining fact for that predicate, return missing-governor[CAR42-FASTENING-WORK-TO-CHANGE] and stop. The practitioner needs no constructor or substrate vocabulary for either result.

Author-side replay of the same result. Car 42 predicate-definition episteme Car42FasteningPredicates-v1 declares FasteningWorkChangedAttachment@Car42(work, transformation) with participant order <work, transformation>; the stipulated Work and transformation facts make the named call obtain. Exact local assertion-substrate edition Car42-Claims-v2 then defines typed conjunction over the named work identity, method enactment, applicability, affected referent, work-to-change predicate, criterion, and whole-work or proper-part claim. The narrow positive case closes because every conjunct applies to that receiving use. In the discriminating failure, the same edition receives only a torque result and temporal overlap but no work-to-change predicate; conjunction semantics cannot manufacture the missing conjunct, so the branch returns the same exact missing-governor blocker rather than a negative production claim. Car42-Claims-v2 is a case-local substrate-edition designator, not a new FPF kind, relation kind, or required universal language.

#Incomplete but identifiable Ship 27

In this case, exact ship-identity specification episteme SHIP-ID-2 states the hull-closure rule. Local applicability claim ShipIdentitySpecApplies-2 applies it to exact candidate hull basis Ship27-HullBasis, exact yard context Yard-27, and the ordered candidate boundaries ending at inceptionBoundary. Exact hull-assembly work can close that specification's rule at inceptionBoundary while outfitting, software installation, trials, and commissioning continue. The resulting inception claim concerns when Ship 27 first exists and remains indexed by SHIP-ID-2 and ShipIdentitySpecApplies-2.

Continuing edition and lineage-aware refresh. Yard identity-governance system YardIdentityGovernanceSystem performs exact revision Work ShipIdentityRuleRevisionWork-2R under obtaining role assignment ShipIdentityRuleReviserAssignment-2R; that Work enacts ShipIdentityRuleRevisionMethod. C.2.P recovers the source expression hull assembly closes Ship 27 identity in SHIP-ID-2. Case-local source-use predicate usesAsRevisionSource(work, sourceEpisteme) is declared, and its case facts make usesAsRevisionSource(ShipIdentityRuleRevisionWork-2R, SHIP-ID-2) obtain. SHIP-ID-2R has a separately recovered C.2.1 identity and ClaimContent hull assembly plus installed propulsion closes Ship 27 identity. The enacted method treats this exact source use and claim-content replacement as a superseding revision within the maintained ship-identity specification line. Those performer, method, source-use, and content-change facts satisfy C.2.1's historical-continuation predicate. Relation occurrence ShipIdentitySpecEdition-2-to-2R : EpistemeEditionRelation therefore obtains with exact participants <SHIP-ID-2, SHIP-ID-2R>; the work and its basis do not become relation participants. A receiving use that follows this lineage refreshes to SHIP-ID-2R, then re-evaluates that exact episteme's applicability at the boundary it now judges. The relation preserves the revision lineage; it carries forward neither the old applicability fact nor a new inception boundary, and it does not rewrite the claim already indexed by SHIP-ID-2.

Non-continuing replacement. SHIP-ID-3 is another exact specification episteme, but this fixture establishes no EpistemeEditionRelation from SHIP-ID-2 or SHIP-ID-2R to it. A later date, similar ship terminology, and use by the same yard do not make it an edition. A use selecting SHIP-ID-3 must establish its applicability independently and publish a separately qualified claim or exact blocker; lineage-based refresh cannot substitute it for either earlier specification. Thus the continuing edition reopens dependent current uses through the named lineage, while the non-continuing replacement opens a new applicability question without altering earlier claims.

Exact author-side substrate edition YardIdentityHistory-v3 defines time-indexed conjunction over the named work, applicability, actual-effect, work-to-change, change-to-identity, and identity-satisfaction claims plus earliest selection over its declared ordered candidate-boundary domain. The positive replay returns exact boundary tI because SHIP-ID-2 is false at every earlier candidate boundary and true at tI; exact work and transformation witnesses remain named. In the discriminating failure, a snapshot substrate can conjoin facts at tI but supplies no ordered boundary domain or earliest-selection law. That substrate cannot establish inception even if a later image satisfies the rule, so the branch returns the exact missing-substrate blocker rather than treating first observation as first existence. The example adds no universal earliest operator or arbitrary minimal-work selection.

An IMO ship identification number may designate Ship 27 and remain stable across later flag, name, ownership, or type changes. The current IMO integrated scheme nevertheless states that number allocation does not define ship status. The number therefore supports regulated designation and continuity only; it neither supplies SHIP-ID-2 nor proves inceptionBoundary. If the receiving use cannot recover a separate applicable ship-identity rule, the inception branch returns the exact identity-governor blocker.

A larger exact production-work occurrence contains the identity-closing work and later work through declared A.15.1 part relations. Production completion occurs only when Ship 27's actual state satisfies the applicable completion criterion at completionBoundary. Delivery, class acceptance, and operational release remain separate. The sentence the yard produced Ship 27 is admissible only after the writer names the intended Work occurrence or extent and says whether the claim concerns Work participation, first existence, or completion.

#Nested and concurrent attribution

Factory work may contain project work, subassembly work, identityClosingWork, and completion-closing work. Every selected work-part relation remains explicit. Jointly necessary concurrent work parts use exact composite work under A.15.1. Two incomparable minimal work composites yield two local inception claims, each indexed by its exact identity-specification episteme and applicability basis. Nested or concurrent attribution creates no additional inception occurrence, and none of those work compositions establishes transformation composition. The identity-specification and completion-criterion epistemes remain cited by the local claims; each applicability basis remains its named predicate or filled local claim; and any C.2.1 edition relation between such epistemes is separate. None is a work participant.

#Pressure adjustment without entity inception

A dated pressure-adjustment Work occurrence may enact an exact pressure-adjustment method, while A.3.4 independently identifies a pressure transformation. Open a positive Work-to-change claim only when the subject practice supplies a named predicate with Work and transformation participant positions and the case facts make that predicate obtain; otherwise keep the two occurrences separate and return missing-governor[pressure-work-to-change]. If the affected vessel or process already exists and no production-completion criterion is current, even the positive route closes as work plus actual change, not as production work, entity inception, or completion.

#PumpSkid assembly before PumpSkid identity

Mounting, wiring, fluid-connection, and whole-configuration changes may each be independently identified under A.3.4, and exact work parts may be grounded under A.15.1. The PumpSkid inception claim may proceed only when a named applicability predicate or filled local claim applies the exact PumpSkid identity-specification episteme to the candidate configuration and boundary, and named Work-to-change and change-to-identity predicates obtain for the actual participants and case facts. A missing applicability or link returns its exact blocker. A claim that additionally requires positive composite-transformation identity or transformation parthood stops at missing-governor[transformation-composition]; Work or method decomposition supplies no proof of transformation decomposition.

#Completion persists after later destruction

In this case, exact production work satisfied criterion episteme PC-3 at boundary tC, and a later accident destroyed the product. Exact author-side substrate edition CompletionHistory-v1 defines boundary-indexed conjunction over production-work identity, applicability of PC-3, and the governed subject-state facts at tC; it does not apply an earliest operator. The positive replay therefore retains the historical completion claim at tC, while the destruction is a later transformation. In the discriminating failure, an unindexed current-state predicate or later completion certificate supplies no satisfiedAt(tC) constructor semantics. That substrate returns the exact missing-substrate blocker for the historical claim rather than moving completion to the certificate or current state. Current evidence, availability, replacement work, acceptance status, and insurance decisions remain separately governed.

#Non-agentive biological synthesis

A spontaneous reaction or biological growth process may be independently grounded as one or more actual transformations under A.3.4. The transformed biological, chemical, or physical referent may itself be a U.System; that fact neither makes it the performer nor supplies production work. If no exact performing System holds the performer position in an obtaining U.RoleAssignment and is grounded as enacting an applicable method in one dated Work occurrence admitted under U.Work, A.15.PROD opens no production-through-work claim. Retain the transformed referent and transformations. Evaluate entity identity only with the biological practice's named identity predicate; if no such predicate is available, return the exact identity-governor blocker. Batch B17, a sample label, first observation, or process record supplies none of the performer-side basis, work identity, or production attribution.

If an exact performing System holds the performer position in an obtaining role assignment, enacts a method in dated Work, and a named applicability claim applies that method to this biological case, the relevant A.15.PROD branch may open. Entity-identity inception still needs the applicable identity-specification episteme plus named Work-to-change and change-to-identity predicates or filled local claims; production completion still needs its applicable criterion episteme, boundary, and criterion-satisfaction facts. The same observed growth can therefore support an actual-change claim while the production-work claim remains blocked; the transformed referent remains present in either result and is not erased when the performer-side basis is absent.

#Scrum Increment before review or release

In this case, the current Scrum Guide and one exact organizational Definition of Done episteme govern a software-product use. When exact Product Backlog item PBI-84 first satisfies that applicable Definition of Done at boundary tD, exact Increment-I84 is born under that practice; work that does not meet the Definition of Done is not part of the Increment. Multiple Increments may exist before Sprint Review, and the review is not a release gate.

A.15.PROD may therefore use the exact applicable Definition of Done episteme as the branch-specific identity and completion criterion at tD, while keeping Sprint Review, delivery, and release separate. The guide does not identify the exact A.15.1 Work occurrence, performer-side basis, actual effects, or work-to-change links. Missing independently obtaining relations involving the Work occurrence, that criterion episteme, or its applicability to PBI-84 yields the corresponding work, criterion, applicability, or boundary blocker rather than a production inference from a Sprint, ticket, review, or release label.

#ReleaseBinary 12: complete build-to-inception replay

BuildOps asks one question: when did exact ReleaseBinary_12 first exist? Verification, transfer, release, deployment, publication, and availability are not part of this answer. The fixture uses one affected referent and one transformation; it does not hide an unnamed effect chain.

Ordinary replay. The runner performed the named Work under the applicable build method. The named work-to-change predicate connects that Work to the store-population transformation; the named change-to-identity predicate says that this transformation made the applicable binary-identity rule become true first at 09:11. The readable answer is: ReleaseBinary_12 first exists at 09:11 through this build Work; decide completion and later uses separately.

Nearest failing variant. Keep every fact above, including the result binding, store transformation, work-to-change predicate, identity specification, applicability, ordered boundaries, and the state that satisfies the identity rule at 09:11, but remove only the declaration and obtaining fact for StorePopulationClosedBinaryIdentity@BuildOps-v12. The exact result is missing-governor[RELEASE-BINARY-CHANGE-TO-IDENTITY] for <ArtifactStorePopulationTransformation_12, ReleaseBinaryIdentitySpec_v12, BuildOutputBasis_12, 09:11, ReleaseBinary_12>. A timestamp, completed write, or builtBinary binding cannot replace that missing change-to-identity predicate.

Author-side replay of the same result. Case substrate ReleaseBinaryInceptionClaims-v1 defines a time-indexed conjunction over the named Work, performer basis, method applicability, the performed storeWrite application fact (not the later result binding), affected referent, transformation, work-to-change predicate, identity specification, applicability claim, and change-to-identity predicate. Its declared ordered boundary domain is 09:00-09:12 and its earliest-satisfying rule returns 09:11, so the positive replay yields ReleaseBinary12InceptionClaim. In the failing variant the same constructor lacks exactly the change-to-identity conjunct and returns missing-governor[RELEASE-BINARY-CHANGE-TO-IDENTITY], exactly as the ordinary replay does. These case-local predicates and this substrate introduce no universal production, work-to-change, or change-to-identity relation kind.

#Bias-Annotation

Scope limitation and five-lens coverage. These annotations cover the three production-recovery branches and their named neighboring claims; they do not classify production language outside a current A.15.PROD use. Gov covers criterion, applicability, and historical-authority errors; Arch covers branch, neighbor-owner, and omnibus-relation errors; Onto/Epist covers work, change, entity, claim, record, and publication distinctions; Prag covers receiver-first selection, useful stops, and exact blockers; and Did covers the familiar verbs, visible final steps, labels, and records that make the overreads plausible.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

In the selected cases and declared receiving uses, no need for a universal production relation kind has been demonstrated. Each current question closes through declared predicates, the case facts that make them obtain, and one branch-local claim or exact blocker. This is a bounded current parsimony result, not proof that every production relation is reducible or that no irreducible production-relation fact can occur in another subject practice. The bases vary across manufacturing, construction, biology, software, formal work, and epistemic production; local compound claims preserve those subject differences and expose a missing predicate instead of hiding it behind a broad relation name.

A later subject practice reopens A.6.RCD when several named claims reuse the same participant meanings or when a named later action must refer again to the same obtaining relation occurrence. Repeated predicate use alone stops at a reusable predicate-definition episteme. A derived-kind candidate additionally states obtaining, applicability, base dependencies, recurrence, and stable relation-occurrence identity. A primitive candidate additionally requires failed lossless derivation, one action-facing distinction lost by every accepted derivation, and independent receiving uses. A.15.PROD records the present no-mint disposition but neither forbids nor pre-admits a later subject-specific derived or primitive relation kind.

The three-question split also preserves time correctly. Work may begin before an entity exists and continue after it first exists. Completion may occur at inception or later. Delivery, acceptance, release, publication, and availability may occur later still. Keeping each boundary and criterion separate gives practitioners useful historical claims without treating every neighboring event as part of production identity.

#SoTA-Echoing

Current Scrum, maritime-identification, and NASA systems-engineering practice supplies three narrower operational answers for identity or completion boundaries. Manufacturing-information, product-information lifecycle, event-log, constructional-ontology, and provenance sources remain useful comparators with different and explicitly limited roles. None of these traditions supplies one universal production ontology or a cross-domain answer to every A.15.PROD branch.

FPF synthesis scope. The three-claim decomposition is an FPF-scoped architectural hypothesis for receiver-specific production recovery, not a claim that the cited traditions share one production ontology. The SoTA-bearing rows below govern only their named practice branches. No current primary source in the reviewed set answers the cross-domain A.15.PROD:4.3 question of when exact Work is the whole production Work or its proper part; that branch remains a bounded FPF hypothesis built from A.15.1 Work identity and the case's declared work-part, method-applicability, Work-to-change, identity-applicability, and completion predicates or filled local claims. A subject domain that demonstrates a different best-known answer, failed lossless derivation with an exact action-facing loss, direct obtaining and applicability laws, independent receiving uses, recurrence, and stable relation-occurrence identity reopens the affected branch and A.6.RCD continuation.

The practical source-use result is visible in the Solution, checklist, and cases: Scrum supplies a Definition-of-Done boundary without review/release collapse; NASA systems engineering supplies a tailored realization criterion without transition/delivery collapse; and IMO supplies stable designation without status/inception collapse. The remaining comparators constrain information and evidence overreads. None supplies the still-hypothetical cross-domain whole/proper-part production-work answer.

#Relations

• Builds on: A.15.1 for exact work identity, work parts, concurrency, and continuity; A.3.1 for production method, intended effect, and applicability; A.3.4 for independently identified actual transformations and the transformation-composition stop; C.2.1 for local claim and predicate-definition epistemes; and A.6.RCD for disposition, derivation, blocker, and any subject-specific continuation.
• Coordinates with: A.1 and the subject-specific pattern that states the candidate's identity rule and applicability; A.15.2 for plans that remain distinct from work; A.15.6 for project and process wording recovery; G.11 when a pinned base definition, substrate edition, or applicability settlement changes; and the declared work-to-change, characteristic-state, evaluation, evidence, assurance, completion-criterion, delivery, acceptance, release, publication, availability, and refresh predicates or patterns selected by the current case.
• Informs: production attribution, manufacturing and construction histories, biological and informational entity inception, rework analysis, product-lifecycle records, completion audits, and P2W or P2S continuation when the receiving action or decision asks one of the three recovered questions.

#Lowering, Repair, and Refresh Conditions

An ordinary production-work claim lowers when exact Work identity, enacted method, method applicability, intended production effect, affected referent, work-part relation, named Work-to-change predicate or filled local claim, shared applicability, or the deciding receiver criterion is missing. An inception claim lowers when its exact identity specification, named applicability predicate or filled local claim, identity-closing Work, actual effects, named Work-to-change and change-to-identity predicates or compound bases, or exact after-side entity cannot be recovered; a claim that this is the first satisfying boundary additionally needs an ordered candidate-boundary domain and earliest-satisfying rule. A completion claim lowers when production Work, applicable criterion, its named applicability predicate or filled local claim, boundary, actual boundary-state facts, or criterion-satisfaction predicate is missing. An ordinary positive claim does not lower merely because no substrate document is materialized. A negative claim needs the selected substrate's applicable negation law, and a pin-triggering or earliest-boundary use needs the constructor, witness, polarity, or time semantics it actually consumes; absence of those required semantics yields the exact missing-substrate blocker. Punctuation, a project, plan, label, result record, log, certificate, or publication supplies no substitute.

A maintainer MUST repair only the affected local claim when later information changes work identity or parthood, a direct work-to-change fact, the exact identity-specification episteme or its applicability basis, the exact completion-criterion episteme or applicability relation, a boundary state, a relied-on base-predicate edition, or the selected substrate edition or constructor semantics. An earlier inception or completion claim remains indexed by the exact specification or criterion episteme and applicability basis used at its boundary. An obtaining C.2.1 EpistemeEditionRelation can trigger lineage-aware refresh of current dependent uses but does not rewrite that claim; a non-continuing replacement opens a new independent applicability question. A later transformation, delivery, acceptance, release, publication, or availability claim does not by itself repair or invalidate an earlier production claim.

A relying practitioner MUST refresh an earlier claim after a change to its exact identity-specification episteme or direct applicability basis, completion-criterion episteme or applicability relation, any relied-on C.2.1 EpistemeEditionRelation, relied-on base-predicate edition, selected substrate edition, constructor semantics, witness or hidden-participant policy, polarity law, temporal policy, work-continuity policy, evidence basis, reference scheme, claim scope, or receiving use. Follow an obtaining edition relation only to discover the continuing later episteme, then re-evaluate that episteme's applicability for the current use. Treat a replacement without that relation as a new identity and do not carry forward lineage or applicability. Refresh claim currentness and reliance separately from the historically indexed occurrence, exact specification or criterion episteme, applicability, and boundary facts.

A maintainer MUST reopen source binding only for the branch whose practice answer changed: a changed Scrum Definition-of-Done rule reopens the software-Increment branch; a changed NASA realization, verification, validation, or transition rule reopens the affected systems-engineering completion use; and a changed IMO identification rule reopens regulated ship designation and continuity, not a generic entity-inception claim. A new source that actually answers cross-domain whole/proper-part production-work attribution reopens section 4.3 and the FPF synthesis hypothesis. A changed comparator reopens only the information, evidence, analogy, or lineage boundary it supports unless a direct subject rule also changes.

#A.15.PROD:End

Last Updated: 2026-07-27 — this section last modified in upstream FPF commit 66e732df (github.com/ailev/FPF)