| 38 | | |
| 39 | | === Subtasks and Progress Tracking === |
| 40 | | The system models subtasks as a decomposition of a !Task, allowing complex tasks to be broken down into smaller, manageable units. |
| 41 | | |
| 42 | | Subtasks are not independently assignable; instead, they are all performed by the worker assigned to the main task. This design ensures consistency and avoids unnecessary complexity in task assignment. |
| 43 | | |
| 44 | | Each subtask includes its own status (e.g., pending, in progress, completed), which enables detailed tracking of progress within a task. |
| 45 | | |
| 46 | | By monitoring the completion of subtasks, the system can provide a more accurate representation of overall task progress and improve transparency for both clients and workers. |
