A mission is a team-level objective of a multi-agent system whose agents act on local information and coordinate through peer and environment interactions, from which system-level progress and constraint satisfaction emerge. Missions group by their dominant deliverable into three functional families — Sense, Organize, Act. The cut is embodiment-agnostic: it applies across aerial and ground robot swarms, underwater vehicle teams, planetary surface rovers, autonomous satellite formations, and teams of reasoning agents — whether they couple mechanically, communicatively, or by observation alone.
The taxonomy classifies the deliverable — what the team is fundamentally producing — not the platform, the sensors, or the coupling modality. Each family draws on its own established line of work.
Build and maintain a shared picture. The team's deliverable is shared knowledge of an environment, system, or set of targets; progress is team-level uncertainty reduction.
Canonical example — shared exploration: a team reduces uncertainty over an unknown region within a time budget; global progress depends on how local observations propagate through inter-agent interaction. The family rests on active perception and its later extensions to distributed and multi-robot sensing.
Form and hold structure & connectivity. The team's deliverable is its own relational state: a target configuration — communication topology, spatial geometry, value agreement, or spatial distribution — produced and sustained as conditions change.
Canonical examples: holding a relay backbone, maintaining a formation, reaching consensus on a value, covering an area. The family rests on graph-theoretic cooperative control, treating consensus, formation, and connectivity as properties of the interaction graph between agents.
Effect change on the world. The team's deliverable is an effect on the world or on a downstream system, produced through coordinated action and a division of work across agents — coupled by shared constraints: capacity, energy, conflicts in shared workspace or shared state, and safety.
Canonical example — precision agriculture: spraying or seeding allocated across a large area within strict resource and safety limits. The family comes out of multi-robot task allocation and the swarm-robotics demonstrations built on it.
Real program-scale deployments set the agenda. Four representative systems, shown as photographs, anchor the families to flown and fielded hardware.
Sense / Organize / Act are the three corners of a barycentric (ternary) simplex with coordinates (s, o, a), s + o + a = 1. A pure-corner mission lives at a vertex; real deployments rarely sit at a single corner. Most are composites — points in the interior of the simplex. We place a handful of widely-cited systems by their dominant deliverable; colour encodes the dominant family (blue Sense, green Organize, orange Act, purple composite).
Reading the interior: Kilobot sits close to the Organize corner for programmable self-assembly; SAGA sits close to the Act corner for allocated agricultural intervention; TERMES sits inboard of SAGA, with an additional Organize share carried by its stigmergic construction rules; DARPA SubT sits near the simplex centroid — a Sense-led mission that nonetheless demands a mesh-maintenance Organize layer and active mobility. Two composites sit firmly inside the simplex: NASA CADRE, just above Kilobot, where autonomous formation driving and a mesh among four lunar rovers (Organize) produce a cooperative subsurface radar map (Sense); and NASA Starling, near the Sense corner, which runs cooperative observation over formation maintenance and an in-space MANET together.
composites & strataSense / Organize / Act are the three canonical families at the deliverable level. We deliberately do not introduce a fourth. Most deployments are composites — interior points of the simplex — and many can be read as special cases of one family inheriting structure from another:
Properties such as adversarial robustness, fault tolerance, and real-time guarantees are likewise not separate families but strata across I–III: any of the three families can be required to deliver under attack, faults, or deadlines. The taxonomy classifies the deliverable; the deployment specifies which strata it must hold up under. We treat the three families as a scaffold rather than a fixed classification — missions that don't fit cleanly push the families to evolve, not the other way around.
scopeThis is the bridge to the project's governing research question: how covert, within-bounds micro-level misbehaviour propagates to macro-level mission failure, and how resilient the mission is. The mission taxonomy supplies the substrate; the adversarial stratum is the cross-cutting layer our work operates in. See the Literature page for the gap analysis and the Theory page for the resiliency formalism.
one reconciled viewAn earlier draft (the Swarm-Resiliency work) organized missions by their coupling modality rather than their deliverable — what binds the agents together. The two cuts are not competitors: the deliverable a team produces and the coupling that produces it line up almost one-to-one. We present them here as one reconciled view: each deliverable family is delivered through a characteristic coupling, with a fourth coupling category (constraint-and-resource) attaching to the Act family's shared limits.
| Deliverable family (this taxonomy) | Coupling category (Swarm-Resiliency) | What binds the agents |
|---|---|---|
| Sense — build/maintain a shared picture | A · Information-coupled | Agents share observations; the deliverable is reduced joint uncertainty. |
| Organize — form/hold structure & connectivity | B · Topology-coupled | Agents are bound by the interaction graph / formation they must hold. |
| Sense (composite substrate) — fused estimate | C · Fusion-coupled | Local estimates are merged into a shared belief; one bad input corrupts the fusion. |
| Act — effect change on the world | D · Constraint-and-resource-coupled | Agents share capacity, energy, workspace, and safety limits while dividing work. |