A.15.PROD:4.7 - 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:
- name the receiving action or decision, state what it must decide, and select one production question;
- recover the exact participants, direct predicates, applicability facts, and boundary facts needed by that question;
- 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
- keep any durable answer in one truthful C.2.1 episteme with exact claim content, one exact
EntityOfConcern, and an effectiveU.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:
| Branch | Least constructor over governed base claims | Hidden-participant, polarity, and time policy |
|---|---|---|
| production-work participation | one typed conjunction over exact A.15.1 work identity, actual method enactment, method applicability and intended production effect, affected referent, direct work-to-change facts, the receiver’s current criterion, and either exact work identity or one exact A.15.1 proper-part relation | every participant and conjunct remains named; no projection hides work, transformation, or criterion witnesses; a negative result requires the selected substrate’s explicit negation law rather than absence of a base assertion |
| entity-identity inception | one time-indexed conjunction over identity-specification applicability, exact work and governed effects, direct work-to-change and change-to-identity links, and satisfaction of the applicable identity predicate, followed by the substrate’s earliest-satisfying-boundary selection over its declared ordered candidate-boundary domain | the candidate basis remains distinct from the after-side entity; work parts and actual transformations remain named or follow the substrate’s explicit witness policy; incomparable minimal work composites remain plural, and A.15.PROD supplies no arbitrary minimization rule |
| production completion | one boundary-indexed conjunction first states criterion satisfaction for exact completionSubject; a second conjunction states exact productionWork, that satisfaction claim, and the declared closure predicate or local closure rule | the claims keep their different entities of concern; no earliest-boundary operator is implied unless separately required, and missing closure semantics preserves satisfaction while blocking only Work completion |
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.