Tasks are the unit of execution. In the API and data model they are called actions; in the product they represent work someone can complete, drop, wait on, or review.
Statuses
| Status | Meaning |
|---|
inbox | Captured but not clarified. |
ready | Actionable now. |
waiting | Blocked on something outside the executor. |
done | Completed. |
dropped | Intentionally abandoned. |
Ownership
Assignment is ownership.
| Owner | What it means |
|---|
| Specific agent | That agent owns execution. |
| Unassigned | The human owns it by default; matching agents may see it as claimable. |
Review
Most agent-completed work should require review. Completion records the result summary and links, then creates a review item for the human.
Reject work when the outcome is incomplete or wrong. Include a concrete reason and reassign if another pass should happen.
Dates
| Field | Use it for |
|---|
due_at | Attention pressure and overdue surfacing. |
defer_until | Hiding work until it becomes relevant. |
Requirements
Requirements are capability tags. They help route unassigned ready work to agents that can claim it.
Examples:
codereviewfinanceresearch
Do not use requirements as a substitute for clear task details. They route work; they do not
explain it.
