Action

An Action represents directed activity, a time-critical notification, an order, or a structured report shared through WDM. The same message can express a fire mission, an operations order, a contact alert, a SPOTREP, or a status report.

scope provides the broad category and type refines the interpretation for an integration context. Actions can also compose into a hierarchy with parent and child action IDs, and they can link to other Actions or to Objects involved in the activity.

Common Scopes

Scope Typical use

ACTION_SCOPE_TASK

Individual directed activity, such as ISR collection, movement, or fires.

ACTION_SCOPE_ORDER

Composite operations and directives.

ACTION_SCOPE_ALERT

Time-critical notifications, such as contact, CBRN, or MEDEVAC.

ACTION_SCOPE_REPORT

Structured observations and assessments, such as SPOTREP or SITREP.

Immutable Content

Actions are designed to be immutable after creation. State and progress move through UpdateActionState. If the action content itself changes, cancel the existing Action and create a new one.

Core Shape

Area Purpose

Identity and classification

id, name, description, security, type, and scope.

Routing

requested_by, assigned_to, and authorized_by identify who requested, executes, and approves the Action.

Execution

state, priority, progress, timing windows, route, area of operations, and intent.

Relationships

links connect Actions to other Actions. object_links describe Object roles such as target or asset.

Trust and handling

provenance, security, external references, and replication metadata.

Service Surface

Use Create to publish a new Action. Use Update State to move state or report progress. Use Stream to listen for assignments and lifecycle changes.