Raft Warfighting Data Model (WDM) Task Service API (1.0)

Query criteria for retrieving tasks from storage.

Uses a flat structure where all criteria are combined with AND logic between fields, and OR logic within repeated fields. Optimized for efficient bulk retrieval. Empty query returns all tasks.

Logic semantics:

• Multiple values within a repeated field use OR (e.g., states=[1,2] means state=DRAFT OR state=PENDING)
• Different fields are combined with AND (e.g., states=[7] AND priorities=[3])

Examples:

Query high-priority in-progress tasks:

{
  "states": [7],
  "priorities": [3]
}

Matches: state=IN_PROGRESS AND priority=HIGH

Query tasks assigned to specific principals:

{
  "assigned_to": [
    {"id": "unit-123", "type": "PRINCIPAL_TYPE_ENTITY"}
  ]
}

Query pending or approved fire missions:

{
  "states": [2, 3],
  "type": ["fire_mission"]
}

Matches: (state=PENDING OR state=APPROVED) AND type="fire_mission"

Query ISR tasks where details.sensor_type is "EO":

{
  "type": ["isr_collection"],
  "filter": {
    "taskPredicate": {
      "field": {
        "fieldPath": "details.sensor_type",
        "comparator": "FIELD_COMPARATOR_EQ",
        "value": { "stringValue": "EO" }
      }
    }
  }
}

Matches: type="isr_collection" AND details.sensor_type == "EO"

Query tasks where details.sensor is EO or IR, and details.priority > 5:

{
  "filter": {
    "and": {
      "statements": [
        {
          "or": {
            "statements": [
              {
                "taskPredicate": {
                  "field": {
                    "fieldPath": "details.sensor",
                    "comparator": "FIELD_COMPARATOR_EQ",
                    "value": { "stringValue": "EO" }
                  }
                }
              },
              {
                "taskPredicate": {
                  "field": {
                    "fieldPath": "details.sensor",
                    "comparator": "FIELD_COMPARATOR_EQ",
                    "value": { "stringValue": "IR" }
                  }
                }
              }
            ]
          }
        },
        {
          "taskPredicate": {
            "field": {
              "fieldPath": "details.priority",
              "comparator": "FIELD_COMPARATOR_GT",
              "value": { "numberValue": 5 }
            }
          }
        }
      ]
    }
  }
}

Matches: (details.sensor == "EO" OR details.sensor == "IR") AND details.priority > 5

Query in-progress tasks:

{
  "filter": {
    "taskPredicate": {
      "field": {
        "fieldPath": "state",
        "comparator": "FIELD_COMPARATOR_EQ",
        "value": { "stringValue": "TASK_STATE_IN_PROGRESS" }
      }
    }
  }
}

Pagination cursor from previous response. Omit or leave empty for first page.

Task lifecycle states.

State transitions follow a general flow: DRAFT -> PENDING -> APPROVED -> ASSIGNED -> ACKNOWLEDGED -> PLANNED -> IN_PROGRESS -> COMPLETED

Terminal states (final, cannot be changed):

• COMPLETED: Successfully finished

• FAILED: Execution failed

• CANCELLED: Cancelled/deleted (the deletion mechanism for tasks)

• REJECTED: Refused by assignee

• TASK_STATE_DRAFT: Being composed - not yet submitted.

• TASK_STATE_PENDING: Submitted, awaiting approval.

• TASK_STATE_APPROVED: Approved by authority, not yet assigned.

• TASK_STATE_ASSIGNED: Assigned to executing principal.

• TASK_STATE_ACKNOWLEDGED: Executing principal acknowledged receipt of task.

• TASK_STATE_PLANNED: Executing principal has developed execution plan.

• TASK_STATE_IN_PROGRESS: Currently being executed.

• TASK_STATE_PAUSED: Execution temporarily halted.

• TASK_STATE_COMPLETED: Successfully completed (TERMINAL STATE).

• TASK_STATE_FAILED: Failed to complete (TERMINAL STATE).

• TASK_STATE_CANCELLED: Cancelled/deleted (TERMINAL STATE). This is the deletion mechanism for tasks - there is no separate delete operation.

• TASK_STATE_REJECTED: Rejected by assignee - unable/unwilling to execute (TERMINAL STATE).

Execution progress within a task's current state.