Task
Execution new in 2.0 since 2.0
aow:TaskA unit of assigned work within a Plan, performed by an Actor filling a Role.
Defines the unit of work that is assigned. A Task is assigned to an Actor. An Action is performed to complete it. A Skill is the capability the Action uses.
Attributes
| Attribute | Type | Required | Description |
|---|---|---|---|
status | one of submitted, working, input-required, completed, failed, canceled, rejected | Where the Task is in its life. | |
due_by | datetime | When the Task must be completed. | |
description | text | yes | Longer human-readable explanation. |
Every entity also has an id and a type, and may carry label, description, and the provenance facet: version, created_at, created_by, revision_of.
Relationships
| Relationship | Points to | How many | Required | Meaning |
|---|---|---|---|---|
shaped_by | Context | many | Context that gives the Intent or Task its situational meaning. | |
concerns | Work Item | many | The Work Item the Intent, Task, or Action is about. | |
constrained_by | Policy | many | Policies that apply. | |
requires_assurance | Assurance Level | one | The highest Assurance Level at which this work may be done. The effective level is the lowest of the Intent's, the Task's, the Skill's, and the performing Agent's autonomy_level. | |
depends_on | Task | many | Tasks that must complete before this one can start. | |
assigned_to | Actor | one | The Actor responsible for performing the Task. | |
requires_role | Role | one | The Role an Actor must fill to take the Task. |
Pointed to by
| From | Relationship | Read backward as |
|---|---|---|
| Plan | has_task | part of plan |
| Task | depends_on | prerequisite of |
| Action | fulfills | fulfilled through |
| Observation | about | observed by |
Notes
Task states match the task states of the Agent2Agent (A2A) protocol, so Tasks can be exchanged over A2A without conversion.
Alignments
| Standard or protocol | Term | Correspondence |
|---|---|---|
| Agent2Agent (A2A) | Task | closeMatch |
| BPMN 2.0 | Task | relatedMatch |
Example
Source: examples/claims-processing.jsonld. The example passes all validation checks.
{
"id": "task-extract-84933",
"type": "Task",
"description": "Extract claim metadata from the claim form.",
"status": "completed",
"concerns": [
"claim-84933"
],
"assigned_to": "agent-validation",
"requires_role": "role-eligibility-processor"
}