DRACO Design of Resilient Architectures for Computing

SHARKS

Primary Research Question: Which of biology's collective behaviors survive a change of mission, an adversary inside the group, and a real flight computer?
Sponsored by
SHARKS research poster.
SHARKS research poster.

Biology has been running swarm coordination for a few hundred million years under constraints an engineered system would call unreasonable: no coordinator, no shared clock, no reliable channel, and a per-agent compute budget measured in neurons. It also ran it under attack the entire time. A school’s response to a predator, an ant colony’s foraging network, a hive deciding where to move — each of those was selected in the presence of predators, cheats, and mimics. Engineered swarms are usually designed for benign conditions and hardened afterward. Biological ones never had that option.

SHARKS takes that seriously rather than decoratively. We work from collective mechanisms drawn from biology and ask two questions of each one: what missions can it actually accomplish, and what does an adversary get to do to it.

Missions

Coordination research tends to fix a single task — usually formation-keeping or encirclement — and optimize it. That hides the more useful result, which is that a mechanism well suited to one mission is often badly suited to the next. We are building out a portfolio and characterizing where each mechanism belongs:

Adversaries

A swarm’s signaling system is an attack surface, and biology has been exploiting that surface for as long as the surface has existed. The mechanisms above are attractive precisely because agents act on cheap local evidence without auditing each other, which is also exactly what an adversary is buying:

Bio-inspiration earns its place or it does not. A mechanism copied from an organism has to beat the engineered baseline on the mission in question — an algorithm is not better for having a good story attached to it. Two failure modes are worth naming up front: taking the metaphor instead of the mechanism, and inheriting robustness that was only ever robustness against one specific historical adversary. A defense that evolved against a particular predator is not a general defense, and neither is an algorithm derived from it.

The lab’s earlier work on defensive strategies for decentralized lightweight swarms is where the adversary side of this starts. Simulation is where the algorithms start, not where they are judged: SHARKS flies on PUPS, the lab’s untethered swarm platform, which exists so that coordination claims have to survive real radios, real batteries, and real timing. Biological mechanisms tend to be cheap, and much of their appeal at drone scale is exactly that — but cheap in a beehive and cheap on a microcontroller are different claims, and only the second one can be measured here.

Open questions