F.15:13.1 - Activity and task under two run schemes

The slice resolves activity under PROVORunScheme-2026 and task under IEC61131RunScheme-2026 as two exact F.17 SchemeSenseCells. A named comparison use is current.

F.15 result:

• SCR-F15-S3 checks each exact triple; shared run-language does not merge them.
• SCR-F15-S12 requires an obtaining F.9 occurrence before the comparison uses a semantic relation. Its Card is optional and its bounded-use claim is separate.
• Any F.17 row must pass its own gate. It may contain the exact cells needed by the row use; table shape does not create the row.
• An ExecutionSystemRoleKindDescription remains an F.4 episteme about one exact local ExecutionSystemRole under one scheme; it does not describe both cells, assign a system, or prove work.
• If a later task sense becomes cyclic while the activity sense remains non-periodic, RSCR-F15-E4 and E9 compare exact later cells and Bridge candidates; evidence may change the use claim or reliance without silently rewriting the prior Bridge.

Suppose CheckRun-17 is dated assessment U.Work, CheckMethod-17 is its semantic U.Method, CheckInterval-17 is the Work interval, and HarnessSystem-17 is the containing System. Evaluator-17 is the admitted U.System that performs the Work using that Method during CheckInterval-17. First recover Evaluator-17’s A.13 core for this action, including declared assignment species EvaluatorAssignmentSpecies-17 and one obtaining occurrence EvaluatorAssignment-17 with every required participant value, Evaluator-17 as holder, and interval coverage. A.15.1 then independently admits CheckRun-17 from its performance history, enacted Method, interval, and containing-System relation. Because this example also claims performance under EvaluatorAssignment-17, F.6 afterward links the already admitted Work to that same assignment.

ApplySCR-S12-17 is the exact A.6.1 rule application and bindings. BridgeRuleResult-17 is a separate C.2.1 result claim; WitnessTrace-17 and its A.10 path are separate again. UnificationConformanceRecord-17 merely cites those admitted refs. Publishing the record requires its own E.24.PUB occurrence, form, and carrier.