Durable Web Schedule

English | 中文

This overlay opts one dsh web process into durable Schedule reminders without changing the shipped default Web composition:

dsh web --config examples/web-schedule/cordis.yml

The current overlay supports one-shot reminders created with a positive whole-number after_seconds. The model manages them through schedule_create, schedule_list, and schedule_delete; every result identifies the delivery mode as session-local.

The original Session log owns each reminder. A live root Agent waits, retries after it becomes idle, and records a durable dispatch receipt in the Web conversation. Closing the process or leaving the Session cold stops its in-memory timer without deleting the record; reopening that same Session restores the wait and delivers an overdue reminder. Merely reading cold history never activates it, and a fork does not inherit its parent's reminders.

Create and actual delete operations acknowledge success only after Session persistence confirms their event prefix. A reminder receipt likewise appears only after its dispatch is durable. Schedule does not provide browser, operating-system, email, SMS, or other external notification, and the best-effort model follow-up is not a delivery acknowledgement.

Absolute-time, fixed-interval, and cron rules are not accepted by this layer.