Chronic disease monitoring
DEMO-24 — Recurring Obligation, One Occurrence Missed
Authored demonstration. Not a live employer result.
01 · Situation
A periodic monitoring requirement generates a series of separately due occurrences. One occurrence in the middle of the series is not demonstrated; the occurrences before and after it are.
Illustrative monitoring protocol establishing a recurring obligation with occurrences due every 30 days, each independently closable.
02 · Evidence
What the record holds.
- E1Recurrence rule: every 30 days, each occurrence independently due and closable
Verified · on file
- E2Occurrence 1 (Day 0 window) — completed and documented
Verified · Day 2
- E3Occurrence 2 (Day 30 window) — monitoring repository reviewed through Day 35; no completion record found for this window
Verified · Day 35
- E4Occurrence 3 (Day 60 window) — completed and documented
Verified · Day 61
03 · Obligations / Owners
The chain of responsibility.
- 01
Monitoring team (complete each occurrence within its own 30-day window, per E1 — each occurrence a separately identifiable instance of the recurring rule, not one durable obligation reopening).
04 · Event Type
The classification of the event.
Three separately instantiated occurrence records (E2, E3, E4) under the single recurrence rule in E1.
05 · Verification Result
What verification established.
SUPPORTED for occurrences 1 and 3 (completion documented); INSUFFICIENT for occurrence 2 (repository silence, not affirmative nonperformance).
06 · Projection
What the evidence implies ahead.
Occurrence 2 not demonstrably fulfilled; occurrences 1 and 3 fulfilled; the series is not treated as one pass/fail obligation.
07 · Next Action
The corrective obligation.
Investigate the occurrence-2 gap specifically; do not treat the completed adjacent occurrences as curing it.
08 · Economic Boundary
Where the evidence stops.
Not established.
09 · Engine Answer
What the Engine can and cannot establish.
The recurrence rule in E1 makes each 30-day occurrence independently due and closable. Occurrences 1 and 3 are each supported as completed by their own documentation. Occurrence 2's window was reviewed through Day 35 with no completion record found in that window specifically. The Engine can demonstrate that one occurrence within an otherwise-fulfilled recurring series is not demonstrably fulfilled — this is a gap in one instance, not a failure of the whole obligation, and not proof the middle occurrence never happened.
One of three, not two of three. The series is not one obligation
10 · What Remains Unknown
Outside the Engine's reach.
Whether occurrence 2 was performed and simply undocumented, or not performed at all.