Job model: state machine and task graphs #4

Closed
opened 2026-10-05 05:04:51 +00:00 by rvnminers-A-and-N · 0 comments
Owner

The skeleton treats a job as a flat list of independent tasks. Real plans need dependencies: screen candidates, then run a costlier follow-up on the best ones.

  • Explicit job and task state machines with allowed transitions, in packages/job-model.
  • Task graph (DAG): a task may depend on outputs of earlier tasks.
  • Job cancellation and task timeouts as first-class states.
  • Per-task attempt history: which worker, when, why it failed.
  • Property tests for the state machine.
The skeleton treats a job as a flat list of independent tasks. Real plans need dependencies: screen candidates, then run a costlier follow-up on the best ones. - [ ] Explicit job and task state machines with allowed transitions, in `packages/job-model`. - [ ] Task graph (DAG): a task may depend on outputs of earlier tasks. - [ ] Job cancellation and task timeouts as first-class states. - [ ] Per-task attempt history: which worker, when, why it failed. - [ ] Property tests for the state machine.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Sisyphus/Sisyphus#4