To separate concerns, the journal could be leverage to schedule loading tasks:
```
|-----------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------|
| pros | cons |
|-----------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------|
| - separation of concerns (lister lists and creates origins, no longer schedules) | - the task's policy (recurring, oneshot) is not part of the journal's event |
| - centralize the scheduling logic within that journal client (that could simplify | (that might be triggering a schema migration on the scheduler's part: new origin_type column in task_type table) |
| maintenance and be a step towards T1157) | |
| | |
|-----------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------|
```