Jordan-Hall / Jordan-Hall/browser
[P1][AUTO-01] Durable schedules and source events
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Programme: #1
Epic: #30
## Objective
Provide durable scheduled/event-driven execution with deduplication, missed-run policy and expiry/freshness re-evaluation rather than blindly replaying old intent.
## Scope
- Timers, recurring schedules, condition watches and source-event triggers.
- Local event bus plus connector webhook/poll cursors.
- Durable next-run state, fake-clock support and timezone semantics.
- Debounce/coalescing/deduplication and per-trigger operation IDs.
- Deadline/expiry and missed-run policy after sleep/offline periods.
- Source freshness checks before acting on delayed triggers.
- Execution-location requirement (`this device`, home worker, authorized remote worker).
- Pause/disable/edit/history and failure backoff.
## Correctness rules
- Powered-off devices cannot execute new online work; wake handling reevaluates intent/deadlines.
- Duplicate webhook/poll events must not create duplicate consequential writes.
- Schedule timing never expands action authority.
## Acceptance criteria
- [ ] Duplicate trigger delivery produces one logical scheduled run/operation according to idempotency policy.
- [ ] Sleep/wake does not blindly execute expired risky tasks.
- [ ] Timezone/DST/fake-clock fixtures are deterministic.
- [ ] Source-dependent actions recheck required freshness/preconditions at execution time.
- [ ] Disabled/revoked schedules cannot dispatch new work.
- [ ] History identifies trigger, scheduled time, actual time, execution location and outcome.
## Dependencies
- CORE-02
- CORE-03
- SEC-02
**First phase:** P1
**Maturity target:** P4
**Owner:** platform
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the referenced CORE-02, CORE-03, and SEC-02 dependencies; the issue names no files, tests, or entry points. Define the work against the acceptance criteria: deterministic scheduling, deduplicated delivery, safe sleep/wake and expiry handling, freshness checks, disabled-schedule enforcement, and complete execution history.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100