A.15.1:12 - Existing work-log repair applications

1. Recover occurrence assertions. For existing logs, first recover the exact candidate action, every actual performer System’s A.13 basis, at least one Method actually followed, the extent, and at least one obtaining locally declared containing-system relation; admit the Work only from those independent facts. If precise assignment-bound attribution is current, then recover the same covering assignment occurrence and its separate F.6 relation. Add optional methodDescriptionRef and only those independently obtaining work-to-referent, binding, and resource-use relations on which the receiving claim relies. Do not create Work by creating a record.
2. Recover the work-judgment basis. Name the direct occurrence facts first. Add exact workContinuityPolicyRef, effective reference scheme, scope, or qualification window only when the identity, episode, retry, resumption, or aggregation judgment has more than one defensible branch. Keep any selected MethodDescription episteme, aggregation policy, criterion, and evidence-use relation outside the Work.
3. Record a continuity policy only for an actual ambiguity. Cite exact workContinuityPolicyRef and its named use when an interruption, resumption, replacement, switch, or composite boundary could support more than one segmentation. If direct facts already close a simple uninterrupted case, omit the policy.
4. Separate temporal aspect, temporal Work part, episode, and operational part. Keep a bare interval or aspect with C.27.TA or its direct domain object. Use TemporalPartOf_work only between independently admitted Work individuals when the proper temporal-sub-occurrence predicate passes; use EpisodeOf_work only for an independently admitted event-bounded Work sub-occurrence; and use OperationalPartOf_work only for an independently admitted performed constituent of the whole. Recover any Method factor separately.
5. Name only useful work parts. If no named resource, evidence, KPI, acceptance, repair, aggregation, cross-context reliance, or source-relation return claim depends on the candidate part, retain the independently established relation, evidence slice, or telemetry slice without adding a durable work-part name.
6. Use B.1.4 for temporal roll-up. Cite the exact temporal aggregation and its union, hull, coverage, and non-overlap policy in the KPI rather than recreating it on Work.
7. Use B.1.6 for resource roll-up. Recover the typed resource ledger, evidence basis, allocation, and overlap or deduplication policy there; each contributing performed resource-use relation remains independently obtaining with an exact Work occurrence as a participant.
8. Pull plans out. Keep calendars and planned fillings in exact U.WorkPlan content; establish performed values only through direct relations in which the Work occurrence participates and through exact A.6.1 bindings.
9. Bind actual values directly. For an operation argument or result, name the identified A.6.1 application and its exact binding. For any other participant or parameter, name the declared subject predicate, participant order, and actual values; return the matching missing-governor result when that predicate is absent. Retain MethodDescription defaults and WorkPlan choices as non-actual neighbors.