Project Zymera
Teams of autonomous agents that explore a world while keeping their communication graph connected — and generalize across team size and unseen maps.
A single robot exploring a building is a solved problem in outline: drive toward the nearest unseen boundary, repeat. A team is a different question — the behavior that matters is not in any one machine, but in how their local choices compose into a group outcome.
Two forces pull against each other. Coverage wants the agents to spread out, so the unseen area shrinks fastest. Communication wants them to stay close, because radios reach only so far and a map is worthless if the piece an agent holds never reaches the others. A decentralized team, each agent acting on a keyhole view of the world, has to hold both at once — managing its own connectivity as a resource it spends and recovers while it works.
Zymera studies that tension: how a team covers a world under limited, range-based communication, how the same agents transfer from a small team on a small map to a large team on a large one, and how a fully learned policy can plan far enough ahead to generalize to maps it has never seen.
We describe the team on three levels, coupled by the communication network. The mission is a finite-horizon cooperative Dec-POMDP; the network touches it twice — it shapes what each agent sees, and it shapes how local actions compose into the next state.
| Macro | The mission — a cooperative objective scored at the team level. Success is more than accumulated reward: a team can gain reward while its capacity to continue — its connectivity, its coverage rate — quietly erodes. |
|---|---|
| Bridge | The communication graph — a limited-range, time-varying network. Neighbors exchange a shared belief and each agent fuses what it receives. This is the layer that turns a set of individuals into a team. |
| Micro | The agent — a local observation, a running belief, and a policy. It can only act on what it and its neighbors currently know. |
Because return alone is insufficient, the framework also tracks a diagnostic mission health — the algebraic connectivity of the graph, information quality, task progress — and reads outcomes as readiness, degradation, or failure rather than a single score.
The complete model — the formalism, its definitions, and the resilience measures built on it — is written up separately. Read the formalism →
Every mission runs on one substrate — deliberately small and honest, so a result is about the team and not a generous setup. The environment is where the framework's bridge becomes concrete.
| The world | N agents on an H×W grid with walls and obstacles; discrete moves; a fixed horizon of 100 steps. |
|---|---|
| The view | Partial observability — each agent sees a small local window, never the whole map. It builds its picture of the world over time and from its neighbors. |
| The bridge | A range-limited, time-varying comm graph. Neighbors gossip a shared occupancy belief over a size-invariant graph network, so the same policy runs on a team of 4 or 10. |
A mission is defined by three choices on this one substrate: what the agents share, what the reward reads, and what connected is required to mean.
| Coverage | Reward is the fraction of free cells visited by the horizon, subject to the graph's connectivity staying positive — cover fast, don't fragment. |
|---|---|
| Relay | Reward is keeping a moving lead agent connected back to a base; connectivity becomes redundant — measured by disjoint paths — so a single link failing is not enough to break it. |
| Delivery | Coverage counts only once it is communicated home over a graph that cannot be held continuously; the spread-then-regroup rhythm has to emerge from the objective. |
The environment is a reusable simulator, kept independent of any particular learning pipeline. See the code →
A mission is a team-level objective that emerges from agents acting on local information. Missions group by what the team produces:
Reduce team-level uncertainty — coverage, mapping, search, monitoring.
Produce the team's own structure — a comm backbone, a formation, a consensus.
Divided work under shared limits — energy, capacity, safety.
Real deployments are composites. Zymera's target is the Sense × Organize seam — cooperative-mapping-shaped, where a maintained communication graph is exactly what lets local maps fuse into one shared picture (the family of the NASA Starling and CADRE missions). The concrete instances we build:
Much of the work is honest negative results — each closed door narrows where the real difficulty lives.


Zero-shot rollouts — frozen policies dropped onto worlds they were never trained on. Each shows one full 100-step episode.



