#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, for completion, which subject state satisfied the criterion and which separate governor made that satisfaction close the exact production Work? This pattern answers each question with separate local claims. 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 occur 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 occur 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. A production-work-participation claim concerns exact currentWork; an entity-inception claim concerns exact producedEntity after inception. Completion needs two claims when Work closure is asserted: the state-satisfaction claim concerns exact completionSubject, while the production-work-completion claim concerns exact productionWork and cites the separate closure governor. Keep each in its own C.2.1 episteme when persisted; never manufacture a union concern.

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 subject state satisfies the applicable completion criterion, and which declared predicate or local claim makes that satisfaction close the exact production Work at this boundary?

The practitioner MUST NOT substitute one branch's conclusion for another branch's answer. Shared facts may support more than one branch only through each branch's own predicate and applicability.

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 a later delivery or acceptance claim is used to revise historical completion without a new basis and claim.

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:

First worked replay — Car 42. Apply the common performer/Work route in section 4.2 to FasteningCell-7, NutFasteningWork-42, and their enacted fastening Method. The named Work-to-change predicate, finishing-state criterion, and separate closure rule establish that the Work completed the required fastening; Car 42 already existed. A missing Work-to-change or Work-closure governor returns the exact blocker shown in case 5.1 while preserving the independently established Work, transformation, or state-satisfaction claim.

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 the pattern that defines it for that practice. 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. Dated Work is an occurrence. A 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 filled local claim applies it to the candidate basis and boundary. Entity-identity inception is the first boundary at which that applicable rule becomes true. For completion, a criterion first tests the state of completionSubject; a separate closure predicate or local claim says whether that satisfaction closes productionWork. A measurement or evaluation result is a separately defined value or episteme about its own concern; it is neither the produced entity nor Work 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, identify that claim as one C.2.1 episteme. When the receiving use also depends on availability to an audience through a form or carrier, establish the separate E.24.PUB publication occurrence.

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 subject 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 neighboring object 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 method descriptions, work plans, objectives, commitments, product specifications, evaluation results, and E.24.PUB publication occurrences, forms, and carriers 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 separate and return missing-governor[work-to-change]. Temporal overlap, a common changed referent, a delta expression, a log record, or a post-state picture may supply evidence for those facts; the declared predicate or compound claim and its obtaining facts 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. 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.

#Recover state satisfaction and historically indexed production completion

Completion wording often hides two claims. First ask whether the exact state-bearing subject satisfied the applicable criterion. Then ask whether the subject practice makes that satisfaction sufficient to close the exact production Work.

The state-satisfaction claim names:

• exact completionSubject whose state is judged;
• exact completionBoundary;
• exact productionCompletionCriterion episteme applicable to that subject and boundary;
• the named applicability predicate or filled local claim; and
• the actual boundary-state facts and the criterion predicate they satisfy.

When persisted, this C.2.1 episteme has completionSubject as its exact EntityOfConcern. It says nothing yet about whether Work is complete.

The separate production-work-completion claim names exact productionWork, the exact state-satisfaction claim, the same boundary, and the declared closure predicate or filled local A.6.RCD claim that makes this criterion satisfaction sufficient to close that Work. Its exact EntityOfConcern is productionWork. If no closure governor is available, keep the positive state-satisfaction claim and return missing-governor[production-work-completion]; do not apply a subject-state predicate to Work by metonymy.

Index every historical state-satisfaction and Work-completion claim by its exact criterion episteme, applicability basis, boundary, and boundary-state facts. Later damage, loss, destruction, delivery, rejection, acceptance, release, publication, or unavailability receives a separate claim. Rework or later production Work that closes under an applicable criterion at a later boundary receives another local Work-completion claim.

Entity-identity inception, criterion satisfaction, and production-Work completion remain separate even when they share a boundary. A later evaluation-result episteme may support one of these claims under a direct evidence-use relation; the branch's declared predicates and facts still establish its boundary, subject state, and Work closure.

Past Work and the two completion claims 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 objects and claims defined and tested separately.

Practice-specific criteria stay local. NASA systems-engineering guidance, Scrum's Definition of Done, and similar authoritative practice sources can supply a criterion for the exact subject and practice use they address. Exact A.15.1 Work identity and a subject-practice closure predicate or local claim separately establish whether criterion satisfaction closes that Work. Transition, delivery, review, and release retain their own claims.

#State one local claim and stop

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 exact currentWork for production-work participation and exact producedEntity for entity-identity inception. Completion uses exact completionSubject for the state-satisfaction episteme and exact productionWork for a separate Work-completion episteme. 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, with the subject pattern locating the ClaimGraph that defines 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 defines that candidate-construction branch; A.15.PROD defines no such kind admission by itself.

#Separate recognition from assurance

Recognition branch for ordinary work. Use the three questions in section 1, the branch outcomes in section 4.1, and the ordinary claim rule in section 4.7. Stop with one readable answer or exact blocker; open only the specific semantic replay needed for a negative claim, an earliest-boundary judgement, or an A.6.RCD:4.2 substrate pin.

Assurance branch for authors and high-consequence use. Replay the exact basis in six visible groups:

• Work and Method. Check exact work identity and every relied-on work-part relation, the actual enactsMethod relation, method applicability, and the intended production effect.
• Actual change and entity inception. Check every work-to-change and change-to-identity predicate and retain the explicit non-inference from work or method composition to transformation composition.
• State satisfaction and Work closure. Check every criterion-applicability fact and boundary-state satisfaction fact. Keep the state-satisfaction claim separate from the closure predicate or local claim that closes the Work.
• Claim epistemes and their current basis. Check 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, C.2.1 identity, and the evidence-use relations actually relied on.
• Positive and discriminating cases. Replay both, so removal of one deciding fact blocks only the claim that consumes it.
• Pinned author substrate. When A.6.RCD:4.2 requires a pin, DPF and FPF authors MUST record the selected substrate and edition and expose direct base predicates, applicability, hidden participants, polarity law, boundary domain and ordering, witness policy, and every earliest-boundary rule used by the claim.

Assurance may warrant reliance on the claim. Work, change, entity inception, and completion remain established by their branch predicates and obtaining facts.

Assurance scope by use. Replay only what the actual reliance consumes. A model or declaration checks exact claim content, one truthful EntityOfConcern, reference scheme, participants, predicates, polarity, and boundary indexing. A conformance use checks that the selected branch reaches one grounded answer or blocker and stops. Pattern review additionally checks the worked and discriminating cases, direct-owner boundaries, checklist, and no-mint disposition. Each assurance use assesses the stated claim; it neither widens that claim nor replaces the branch predicates and facts.

#Run the recovery sequence and stop deliberately

The ordinary sequence is section 4.7 applied to the selected branch. If several production questions are current, handle each as a separate claim. For production-work participation, choose the whole-work or proper-part branch in section 4.3; for inception or completion, use sections 4.5 or 4.6. Stop after the readable answer or exact blocker. If later reuse needs a durable claim, identify its C.2.1 episteme; if the receiving use also needs availability through a form or carrier, establish the separate E.24.PUB occurrence. 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 only for an A.6.RCD:4.2 pin-triggering use or when a negative or earliest-boundary answer consumes additional semantics:

1. name the branch-local constructor and, when a pin is required, the exact substrate and edition; expose only the inputs, applicability, hidden-participant or witness policy, polarity law, boundary domain and ordering, and temporal rule that can change this answer;
2. 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;
3. 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
4. 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
  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

#Archetypal Grounding

#Car 42 and the required nut

Identity boundary. Car 42 already satisfies its identity rule before NutFasteningWork-42.

Assignment declaration. Car42FasteningAssignmentSpecies is a directly declared U.SystemRoleAssignment species. Its ordered participant positions are holder and assigned system-role kind; their domains are U.System and Car42FasteningPerformerSystemRoleKindDomain.

Assignment occurrence rule. The species applies to Car-42 fastening Work and says that its holder supplies the fastening contribution as Car42FasteningPerformerSystemRole throughout the declared interval. Holder, assigned-kind value, and that uninterrupted interval identify one occurrence.

Work and Method basis. The common route in section 4.2 is instantiated here: A.13 recovers FasteningCell-7 : U.System through obtaining Car42FasteningAssignment-42; A.15.1 independently admits NutFasteningWork-42 with its enacted fastening Method. Because this case consumes precise assignment-bound attribution, F.6 then relates the admitted Work through the same assignment.

Actual-change basis. A.3.4 separately identifies Car42FastenerAttachmentTransformation. It concerns the same continuing car and does not bring Car 42 into existence.

Whole-work branch for the narrow use. NutFasteningWork-42 can be the whole productionWork when its fastening method is applicable and FasteningWorkChangedAttachment@Car42(work, transformation) obtains for that Work and Car42FastenerAttachmentTransformation.

State satisfaction. At the fastening boundary, Car42FinishingStateSatisfactionClaim has exact EntityOfConcern Car42 and states that the car satisfies Car42FinishingCriterion-v1.

Work closure. Separately, subject-bounded Car42FasteningClosureRule-v1 supports Car42FasteningWorkCompletionClaim, whose EntityOfConcern is NutFasteningWork-42, because the required attachment state is satisfied and no required fastening activity remains for this narrow use.

Wider-work contrast. 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. The verb fasten and narrative order decide none of these claims.

Cold-practitioner replay. Applying section 4.7 to the case facts returns: this Work completed the required fastening for this use; Car 42 already existed. Missing FasteningWorkChangedAttachment@Car42 returns missing-governor[CAR42-FASTENING-WORK-TO-CHANGE]. Missing Car42FasteningClosureRule-v1 preserves Car42FinishingStateSatisfactionClaim and returns missing-governor[CAR42-FASTENING-WORK-COMPLETION]. The author-side counterfactual uses Car42FasteningPredicates-v1 for the Work-to-change predicate and Car42-Claims-v2 for the separate state-satisfaction and Work-completion claims; removing each deciding fact separately reproduces those two results without introducing a universal production or completion relation kind.

#Incomplete but identifiable Ship 27

Identity rule and applicability. 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.

Entity inception before later Work ends. 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.

Ordinary answer. Ship 27 first exists at inceptionBoundary under that exact specification and applicability basis; later Work continues, and production completion remains a separate question.

Continuing edition — assignment declaration. ShipIdentityRuleRevisionAssignmentSpecies is a directly declared U.SystemRoleAssignment species. Its ordered positions are holder and assigned system-role kind, with holder domain U.System and assigned-kind domain ShipIdentityRuleReviserSystemRoleKindDomain.

Continuing edition — assignment predicate. The predicate applies to ship-identity revision Work in Yard-27 under ShipIdentityRuleRevisionMethod. It obtains when the holder supplies that revision contribution throughout the declared interval. Holder, assigned-kind value, Yard-27, and that uninterrupted interval identify one occurrence.

Continuing edition — Work and Method. Applying the common route in section 4.2, A.13 recovers YardIdentityGovernanceSystem through obtaining ShipIdentityRuleReviserAssignment-2R, whose assigned-kind value is ShipIdentityRuleReviserSystemRole and whose interval covers the full Work. A.15.1 independently admits ShipIdentityRuleRevisionWork-2R with the enacted revision Method. Because this branch consumes precise assignment-bound attribution, F.6 then relates the admitted Work through that same assignment.

Source expression and predicate. C.2.P recovers the source expression hull assembly closes Ship 27 identity in SHIP-ID-2. Predicate-definition episteme YardRevisionSourceUsePredicates-v1 declares case-local predicate usesAsRevisionSource(work, sourceEpisteme) with participant order <revision Work, source episteme>.

Source-use obtaining test. The predicate applies only to ship-identity revision Work under ShipIdentityRuleRevisionMethod. It is true only when that Method application opens the source episteme and uses the selected source claim as a premise.

Edition basis. The exact source-use participants are ShipIdentityRuleRevisionWork-2R and SHIP-ID-2. The revision Work opens SHIP-ID-2, selects its hull-closure claim as an explicit premise, and produces SHIP-ID-2R, whose separate C.2.1 ClaimContent says that hull assembly plus installed propulsion closes Ship 27 identity. Those facts make usesAsRevisionSource(ShipIdentityRuleRevisionWork-2R, SHIP-ID-2) obtain.

The applicable continuity rule for this specification family requires exact use of SHIP-ID-2, preservation of the ship EntityOfConcern and listed identity claims, and explicit identification of the corrected claim content without a reference-scheme retargeting. The current source use and preserved and deliberately changed features satisfy that rule, so ShipIdentitySpecEdition-2-to-2R : EpistemeEditionRelation obtains for SHIP-ID-2 and SHIP-ID-2R. The performer, Method, Work, provenance, and replacement facts supply evidence for the test; no label makes continuity true. The lineage carries forward neither old applicability nor a new inception boundary.

Lineage blockers. Keep the two failures distinct:

• If the source-use predicate is not defined, return missing-governor[SHIP-IDENTITY-REVISION-SOURCE-USE].
• If its definition is current but the actual premise-selection facts cannot be recovered, return missing-information[SHIP-IDENTITY-REVISION-SOURCE-USE].

Either result keeps SHIP-ID-2R usable as a separately identified specification episteme but blocks ShipIdentitySpecEdition-2-to-2R. A similar title, later date, common publisher, or bare provenance edge does not restore that lineage.

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 constitute a separately qualified C.2.1 claim or return the exact blocker; lineage-based refresh cannot substitute it for either earlier specification.

The continuing edition reopens dependent current uses through the named lineage. The non-continuing replacement opens a new applicability question without altering earlier claims.

Author-side substrate. Exact 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. It also defines earliest selection over its declared ordered candidate-boundary domain.

The positive replay returns exact boundary tI because the identity predicate stated by SHIP-ID-2 is false at every earlier candidate boundary and true at tI. Exact Work and transformation witnesses remain named.

Nearest substrate failure. A snapshot substrate can conjoin facts at tI but supplies no ordered boundary domain or earliest-selection law. It 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.

Designation is not identity. The current IMO integrated scheme uses an IMO ship identification number as a stable designator across later flag, name, ownership, or type changes and states that allocation does not define ship status. Ship identity and continuity therefore still require their applicable subject rules. If the receiving use cannot recover a separate ship-identity rule for this candidate basis and boundary, the inception branch returns the exact identity-governor blocker.

Larger Work. A larger exact production-work occurrence contains the identity-closing and later Work through declared A.15.1 part relations.

State satisfaction. At completionBoundary, one claim may state that Ship 27's actual state satisfies the applicable completion criterion.

Work closure. A separate yard closure predicate or local claim must connect that satisfaction to completion of the larger production Work. Without it, preserve the state claim and return missing-governor[SHIP27-PRODUCTION-WORK-COMPLETION].

Delivery, class acceptance, and operational release remain separate. The sentence the yard produced Ship 27 is admissible only after the writer selects Work participation, first existence, state satisfaction, or Work completion.

#Nested and concurrent attribution

Work structure. 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.

Plural minimal composites. 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.

Epistemic basis remains separate. 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

Work, Method, and change. A dated pressure-adjustment Work occurrence may enact an exact pressure-adjustment method, while A.3.4 independently identifies a pressure transformation.

Work-to-change claim. Open a positive 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].

Stop. If the affected vessel or process already exists and no production-completion criterion is current, the result records the exact Work, the exact transformation, and their obtaining Work-to-change predicate. The production-work-participation, entity-inception, and completion branches remain unopened.

#PumpSkid assembly before PumpSkid identity

Actual Work and change. 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.

Inception basis. A 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. Named Work-to-change and change-to-identity predicates must also obtain for the actual participants and case facts. A missing applicability or link returns its exact blocker.

Transformation-composition boundary. 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

Historical positive case. The product's state satisfied criterion episteme PC-3 at boundary tC, and the subject-practice closure rule made that satisfaction sufficient to close the named production Work.

CompletionHistory-v1 keeps the Work identity, applicability of PC-3, subject-state facts at tC, state-satisfaction claim, and separate Work-completion claim explicit. The two claims keep their different entities of concern. The history uses the declared boundary and does not apply an earliest operator. Record a later accident and destruction in separate claims while retaining the historical claims at tC.

Nearest historical failure. Keep the later certificate or an unindexed current-state predicate, but remove the semantics that say the subject satisfied PC-3 at tC. The historical check then returns the exact missing-substrate blocker; neither the certificate nor the current-state predicate supplies the missing boundary-indexed satisfaction or Work-completion basis.

If only the closure rule is missing, the state-satisfaction claim remains and only Work completion returns its exact missing governor. Current evidence, availability, replacement Work, acceptance status, and insurance decisions remain separate.

#Non-agentive biological synthesis

Actual transformation. A spontaneous reaction or biological growth process may be independently grounded as one or more actual transformations under A.3.4. The transformed referent may itself be a U.System; the performer question remains separate.

Performer and Work result. Apply the common route in section 4.2. A production-through-Work claim opens only after A.13 recovers every exact actual performer and A.15.1 independently admits dated Work with an applicable enacted Method. This fixture stipulates neither basis, so it retains the referent and transformations and returns the performer/Work blocker. Assignment-bound attribution and F.6 are additional only when the receiving use expressly consumes them; their absence is not itself a Work-membership failure.

Entity inception and completion then still need their own exact identity, state-satisfaction, and Work-closure governors. Do not turn observed growth into the missing performer-side basis.

#Scrum Increment before review or release

Product-state and identity basis. The Scrum Guide and one exact organizational Definition of Done episteme are authoritative practice sources for this bounded software-product use. When PBI-84 first satisfies that criterion at tD, the local product-state and Increment-identity claims may be stated under their exact applicability rules. Work that does not meet that Definition of Done is not part of the Increment.

Review and release stay separate. Multiple Increments may exist before Sprint Review, and review is not a release gate.

Current A.15.PROD use. The pattern may use the applicable Definition of Done for the state-satisfaction or identity question it actually answers, while keeping Sprint Review, delivery, and release separate.

Work-completion boundary. The guide does not identify exact A.15.1 Work, its performer basis, or a local predicate that makes satisfaction close that Work. A Work-completion claim therefore needs an additional subject-practice closure governor. Otherwise keep the product-state claim and return the exact Work-completion blocker.

#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 answer. 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, and the named change-to-identity predicate says that the transformation made the applicable binary-identity rule become true first at 09:11. Therefore ReleaseBinary_12 first exists at 09:11 through this build Work; decide completion and later uses separately. The table below supplies the exact assurance basis for that answer.

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. 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. The positive replay therefore 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. 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.

#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

Scrum, NASA systems-engineering guidance, and IMO regulation are authoritative practice or regulatory sources for their named local questions. They are not treated here as SoTA merely because they are official or widely used. Manufacturing-information, product-information lifecycle, event-log, constructional-ontology, and provenance sources remain bounded comparators. None supplies a universal production ontology or a cross-domain answer to every A.15.PROD branch.

FPF synthesis scope. The three-question decomposition is an FPF-scoped architectural hypothesis for receiver-specific production recovery. The reviewed source set contains no independent best-known comparison that would justify calling Scrum, NASA, or IMO a SoTA answer to the cross-domain architecture. Their rows constrain only their named practice questions. The whole-to-proper-part and Work-closure architecture remains a bounded FPF hypothesis built from exact Work identity, direct predicates, state-satisfaction claims, and subject-practice closure rules. A later best-known comparison can reopen only the affected branch.

The practical source-use result is visible in the Solution, checklist, and cases: the Scrum source supplies a bounded product-state criterion without collapsing review into release; NASA guidance distinguishes realization activities from transition; and IMO regulation supplies stable designation without status or inception. These are authoritative local constraints, not evidence that any one source is the best-known cross-domain production architecture.

#Relations

• Builds on: A.13 for the exact actual performer; A.15.1 for Work identity, Work parts, concurrency, continuity, and independent Work admission; F.6 only for a production claim that consumes precise assignment-bound attribution through the same obtaining A.13 assignment; A.3.1 for the production Method, intended effect, and applicability; A.3.4 for 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 subject-specific continuation.
• Coordinates with: A.1 and the subject-specific identity owner; A.6.1 for an actual application and result binding without treating either as inception; C.2.P for exact source expressions; A.15.2 for plans distinct from Work; A.15.6 for project and process wording recovery; A.10 for an evidence-use or bounded-reliance claim; B.3 for assurance; E.24.PUB for availability through a publication occurrence, form, and carrier; and G.11 when a pinned definition, substrate edition, or applicability settlement changes.
• Coordinates with: the exact characteristic-state, evaluation, completion-criterion, delivery, acceptance, release, 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 its exact Work, Method enactment, Method applicability, intended production effect, affected referent, Work-part relation, Work-to-change predicate or local claim, or the criterion and its applicability consumed by the receiver is missing.

An inception claim lowers when its exact identity specification and applicability, identity-closing Work, actual effects, Work-to-change and change-to-identity bases, or after-side entity cannot be recovered. A claim that this is the first satisfying boundary additionally needs an ordered candidate-boundary domain and an earliest-satisfying rule.

A completion use preserves a valid state-satisfaction claim whenever possible. That claim lowers only when its completion subject, criterion and applicability, boundary, boundary-state facts, or state-satisfaction predicate is missing. The separate Work-completion claim lowers when exact production Work or its closure predicate or local claim is absent; loss of that link does not erase the state-satisfaction claim.

An ordinary positive claim needs no materialized substrate document. A negative claim needs the selected substrate's applicable negation law. A pin-triggering or earliest-boundary use needs only the constructor, witness, polarity, ordering, or time semantics it actually consumes; missing required semantics yields the exact missing-substrate blocker. A representation, record, or publication can carry evidence or a claim but cannot supply those missing semantics.

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-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)