A.15.PROD:1 - 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.