CC-A15.PROD-1 | The receiving use selects production-work participation, entity-identity inception, production completion, or an explicit subset. One branch conclusion is never another branch’s answer; shared facts support each branch only through its own predicate and applicability. |
CC-A15.PROD-2 | currentWork and productionWork designate exact A.15.1 Work occurrences admitted under U.Work, not plans, labels, projects, methods, logs, publications, or records that describe those occurrences. |
CC-A15.PROD-3 | The whole-work branch names actual enactsMethod, method applicability and intended production effect, affected referent, exact work-to-change facts, and the criterion current for the receiver. |
CC-A15.PROD-4 | The proper-part branch names an exact A.15.1 work-part relation and gives the containing work the same grounding required by the whole-work branch. |
CC-A15.PROD-5 | Every actual transformation is independently identified under A.3.4; work, method, samples, temporal subdivision, and flow representations do not imply transformation composition. |
CC-A15.PROD-6 | Every Work-to-change and change-to-identity link names a declared predicate with participant order and obtaining facts or a filled local A.6.RCD claim. Completion separately names the criterion-satisfaction predicate for completionSubject and the closure predicate or local claim for productionWork; neither substitutes for the other. |
CC-A15.PROD-7 | Exact productIdentitySpecification is identified as a C.2.1 episteme before inception without a surrogate future producedEntity; a named applicability predicate or filled local claim applies it to the candidate basis, subject context, and exact inceptionBoundary, and the entity is designated only after that exact applicable rule first holds. Publication availability, when required, is a separate E.24.PUB occurrence. Any claim that this is an edition of another specification names an obtaining C.2.1 EpistemeEditionRelation. |
CC-A15.PROD-8 | A positive inception claim satisfies A15PROD-D1 and names exact identityClosingWork, exact productIdentitySpecification, its named applicability predicate or filled local claim, exact inceptionBoundary, exact producedEntity, and first satisfaction of that exact applicable specification’s rule. |
CC-A15.PROD-9 | Concurrent or nested identity-closing work is composed only through exact A.15.1 work-part relations; incomparable minimal composites remain plural, and each local inception claim retains its exact identity-specification episteme and applicability basis. |
CC-A15.PROD-10 | A completion use first names exact completionSubject, criterion episteme, applicability, boundary-state facts, and state-satisfaction predicate. A separate Work-completion claim names exact productionWork and the closure predicate or local claim that makes that satisfaction sufficient to close it. Missing closure semantics blocks only Work completion. |
CC-A15.PROD-11 | Historical state-satisfaction and Work-completion claims retain their exact criterion episteme, applicability basis, boundary, and boundary-state facts. Rework, a later criterion, damage, loss, delivery, acceptance, release, publication, or availability receives a separate claim. |
CC-A15.PROD-12 | Each local assertion is one C.2.1 episteme with one truthful exact EntityOfConcern, claim content, effective reference scheme, and decided positive or negative polarity; no union concern is manufactured, and unresolved information sufficiency or reliance remains separately evaluated. |
CC-A15.PROD-13 | An unresolved basis is returned as the exact missing-governor, work-granularity, criterion, applicability, boundary-state, or transformation-composition blocker, not as a third predicate value. |
CC-A15.PROD-14 | The current no-mint result introduces no universal production relation kind, U.ProductionWork, relation signature, or relation occurrence and asserts no universal reducibility. A later subject-specific candidate requires A.6.RCD only when a named later action must reidentify the same obtaining relation occurrence; its definition states obtaining, applicability, base dependencies, recurrence, and occurrence identity. A primitive candidate additionally demonstrates failed lossless derivation, one action-facing distinction every accepted derivation loses, and independent receiving uses. |
CC-A15.PROD-15 | Recognition and assurance remain separate. Evidence and evaluation can support a branch claim; the branch predicates and obtaining facts establish Work, transformation, entity inception, or completion. |
CC-A15.PROD-16 | The produced entity, measurement or evaluation result, delivered entity, acceptance verdict, release, publication, availability, and downstream effect remain distinct; each positive claim names its declared predicate or its own subject pattern, and a missing predicate returns the corresponding blocker. |
CC-A15.PROD-17 | A practice-specific source is used only for the branch question it answers: a stable identifier does not establish entity status or inception; a systems-engineering realization criterion does not collapse transition into completion; and a Scrum Definition of Done does not supply work identity, effects, review, or release. |
CC-A15.PROD-18 | An ordinary positive local claim names its governed base facts, the exact Method and/or criterion applicability consumed by its branch, readable conjunction, answer, and stop without requiring a substrate document. A pin-triggering use names the exact substrate and edition and replays only the constructor semantics it consumes. A negative or earliest-boundary claim exposes its polarity, witness, boundary-domain, ordering, or selection law; unavailable required semantics returns the exact missing-substrate blocker. |