Concept
Listener vs proactive workers
Listener workers wait for external events and are fully implemented; proactive workers run on schedules and are typed but not executed yet in v0.1.
Problem
Choosing the wrong worker type leads to polling where you should listen, or dead code where the scheduler is not yet live.
Mental model
listener = something calls you; proactive = you run on a clock.
| Type | Behavior | Status |
|---|---|---|
listener |
Waits for external events (HTTP webhooks, queues, etc.) | Implemented |
proactive |
Runs on schedule / interval / cron / API poll | Types only (coming soon) |
A listener implements start(ctx)/stop(ctx) and registers routes on ctx.http. A proactive worker declares a schedule and an execute(ctx) body.