Transitional care program
DEMO-37 — Scope Cessation, Predicate No Longer Applies
Authored demonstration. Not a live employer result.
01 · Situation
An obligation is valid only while the subject remains within a defined program scope. A transfer moves the subject out of that scope partway through the obligation's window. A deadline that had already passed before the transfer is evaluated independently.
Illustrative program-participation protocol (E1), defining the scope predicate as “actively enrolled in the transitional care program,” with a weekly check-in obligation due every 7 days while that predicate holds.
02 · Evidence
What the record holds.
- E1Program protocol, defining the scope predicate and the weekly obligation
Verified · on file
- E2Week 1 check-in, due Day 7 — completed
Verified · Day 6
- E3Transfer record: subject discharged from the program, scope predicate ceases effective Day 10, 14:00
Verified · Day 10
03 · Obligations / Owners
The chain of responsibility.
- 01
Care coordinator (weekly check-ins while the scope predicate holds, per E1).
04 · Event Type
The classification of the event.
ExecutionClaimed — E2 claims completion of Week 1. EvidenceAttached — E1–E3 are attached. EventObserved — E3 records the transfer and exact cessation of the scope predicate. VerificationCompleted — Week 1 and the truncated Week 2 applicability period are evaluated independently.
05 · Verification Result
What verification established.
Week 1 check-in: SUPPORTED as fulfilled, evaluated independently since it was due before the transfer. Week 2 applicability: the scope predicate is affirmatively shown (E3) to have ceased at 14:00 on Day 10.
06 · Projection
What the evidence implies ahead.
Week 2 became applicable while the subject remained enrolled, but its applicability ceased at 14:00 on Day 10 under E1's scope terms, before the Day 14 deadline. No performance is required after scope cessation, and no missed deadline is projected.
07 · Next Action
The corrective obligation.
None — Week 1 was properly closed before transfer; no obligation exists to act on afterward.
08 · Economic Boundary
Where the evidence stops.
Not applicable.
09 · Engine Answer
What the Engine can and cannot establish.
E1 makes this obligation conditional on active program participation. Week 1's check-in was due and completed before any transfer occurred, and is evaluated on its own terms as fulfilled. E3 shows the scope predicate ceased at 14:00 on Day 10 — before Week 2's Day 14 due date. The Engine can demonstrate that Week 2 became applicable while the subject remained enrolled, but that its applicability ceased before its deadline arrived — not because it was cancelled or unfulfilled, but because the governing artifact's own scope condition no longer applied by the time it would have come due. This is distinct from cancellation: no authority acted to cancel anything; the predicate simply stopped holding.
Week 1 closed before the transfer. Week 2 never got the chance to be missed.
10 · What Remains Unknown
Outside the Engine's reach.
Nothing material; this record does not address whether a different program's obligations began at the new facility.