Task Service

task service owns task definition, scheduling, execution, and auditable artifacts.

What you get here

• how task definitions are stored in .ship/task/<taskId>/task.md
• how scheduling works via unified when
• how execution differs in agent and script modes
• how final states are derived (executionStatus / resultStatus / status)
• how live progress is exposed in Console UI (run-progress.json)

Doc map (recommended order)

1. Task Definition and Action Contracts
2. Agent Task Mode
3. Script Task Mode
4. Scheduler Registration and Trigger Flow
5. Execution and Validation Flow
6. Run Artifacts and Debugging

Runtime boundary

• task does not send chat messages by default.
• run is async-accepted and returns accepted=true plus executionId immediately.
• Results are written into run directories by default.