A.15.1:5.1 - Parts and wholes of Work (occurrence facts)

• Temporal-part (TemporalPartOf_work). Both participants are independently admitted Work individuals. The first is a proper temporal sub-occurrence of the second under the §4.1a predicate, with its own exact extent and performed content. Use it when a later resource, evidence, KPI, acceptance, repair, or aggregation claim needs that Work part as an individual. A bare interval, telemetry window, or evidence slice stays a C.27.TA temporal aspect or its direct domain object; it is not the first participant of TemporalPartOf_work.
• Episode-part (EpisodeOf_work). Both participants are independently admitted Work individuals. The first is an event-bounded performed sub-occurrence of the second under the §4.1a predicate. Entry, resumption, mode switch, switch-to-method, interruption, switch-away, completion, or a declared pause may supply candidate boundary events. Cite an exact workContinuityPolicyRef only when direct facts permit more than one grouping for the named use; timestamps, a policy, or an episode-looking label alone establish no episode relation.

workContinuityPolicyRef designates the exact C.2.1 episteme whose claims state the named use, boundary events, tolerated variation, and branch criterion. Interpret those claims under that episteme’s effective U.ReferenceScheme. Add a U.ClaimScope, temporal qualification window, or model-use structure only when changing it changes the segmentation assertion; otherwise omit it. The policy episteme supports classification of the already existing history for that use. A later or competing policy episteme can support another identity or segmentation assertion. Call it an edition only when an exact C.2.1 EpistemeEditionRelation obtains between the exact earlier and later epistemes; without that relation it is a non-continuing replacement. Either way, the policy neither becomes a U.MethodDescription by policy form nor changes the occurrence, its parts, or their actual facts.

• Operational-part (OperationalPartOf_work). A work-part occurrence that may enact a factor of a recovered U.Method, for example, an incision occurrence within an appendectomy occurrence, possibly overlapping with others in time. If a method-description reference is used, it identifies, describes, constrains, or evidences that method factor; the referenced U.MethodDescription is not enacted. If no U.Method factor is recovered, keep the material as the work part, evidence segment, telemetry segment, mechanism material, system-component behavior, or missing-source-relation note that was actually identified; do not infer a method factor from its label.
• Concurrent work parts (derived use-side reading; no fourth parthood relation). First state each exact work-part relation to the same parent. Then use C.27.TA to state the exact temporal-overlap predicate, reference, intervals, and use. If a claim also says that the parts were coordinated, name its declared coordination predicate and actual participants. Shared parentage and overlap do not by themselves establish coordination, and ConcurrentPartOf_work is not introduced as a primitive work-part relation.

Naming threshold. Do not mint a durable public U-kind or durable named work object, or infer a separate work occurrence for every interval, telemetry segment, pause, or episode-looking wording. Use a derivative part relation for an independently admitted Work part; give that part a durable name only when downstream use needs its own resources, evidence, KPI, acceptance, repair, aggregation, cross-context reliance, or source-relation return use. In other cases keep the temporal relation, evidence slice, telemetry segment, method-description constituent, missing-source-relation note, or other concrete neighboring object that the task actually needs.

Didactic rule: Method composition is not proof of Work decomposition, and Work decomposition is not proof of method composition. A temporal work part may enact the same whole method during a slice. An episode may continue one method or mode, span several operational parts, or repeat the same method fragment; an evidence policy may support a finer segmentation claim without changing method identity. An operational part may correspond to a method factor only when that factor is recovered as U.Method.

Quick choice test.

• Ask “do I need only an interval or aspect, or an independently admitted Work sub-occurrence?” Use C.27.TA or the direct temporal object for the first. Use TemporalPartOf_work only for the second, after its proper-sub-occurrence predicate passes.
• Ask “does this named use need an event-bounded fragment of the parent?” If yes, recover the candidate boundary events. Cite workContinuityPolicyRef only when interruption, resumption, switch, replacement, or pause leaves the grouping ambiguous for that use; then use EpisodeOf_work only when its direct predicate is satisfied.
• Ask “which performed sub-occurrence has its own actual performer System with an A.13 basis, temporal extent, enacted Method, affected referent, bindings, resource use, or separately consumed place in an aggregation?” If that is current, use OperationalPartOf_work or another declared Work-part relation. When precise assignment-bound attribution is also current, check the separate F.6 relation only after admitting the sub-occurrence. A neighboring evaluation or effect claim does not establish Work parthood by itself.
• Ask “which way-of-doing part is being composed?” If the answer needs preconditions, effects, interface, and whole-method relation, recover a U.Method submethod under A.3.1 and B.1.5; do not make the work part itself carry the method identity.