SWARM — 05. One Living System David-narrated instructional simulation replay [00:00 · simulation 00:00] Use every family under a known strain Mission five completes our introduction to all nine families. We have three arrays, a twelve-minute deadline, and requirements of ninety survivors and one modular carrier. The preview also shows high energy demand from one minute thirty to two minutes five. We can prepare for that disruption instead of discovering it through failure. [00:22 · simulation 00:00] Local alignment strengthens the formation I select the two blue Coordination core craft in the inner swarm. Nearby small craft align and cohere more strongly around them, while separation rules help prevent crowding. These are local influences within the formation. They are another specialist contribution, alongside scouting, protection, energy, and repair, rather than a command I must issue to each drone. [00:49 · simulation 00:00] Engagement consumes the support margin I highlight the thirty-six red Battle wing drones. They engage revealed contacts when they are close enough and have energy. Watch their reserve fall during work, then watch low-reserve craft return toward support. That is why contact progress alone is not a readiness indicator. The battle wing depends on the other families to keep contributing. [01:22 · simulation 00:10] Control time and the map view I demonstrate the speed control, then Fit or Follow to change how I read the map. Fit gives the full route; Follow keeps the carrier layer in view. Zoom helps separate individual drones. Speed changes how fast game time passes, not the rules. I slow or pause whenever a decision needs closer attention. [02:33 · simulation 01:20] Prepare before the disruption begins At one minute twenty, the ten-second warning appears. Higher energy demand is about to begin. I read the forecast alongside our wing reserve and integrity, and use regrouping to bring the drones toward support. A known disruption is a planning opportunity. The countdown remains visible, so I can tell when the extra demand begins and ends. [03:00 · simulation 01:30] Hold the support connection through the strain The energy-demand window has begun. I keep the wing near support and watch reserve, delivery, and repair as time passes. Simply owning a full energy chain does not guarantee it will cope with every push. Our formation and timing affect whether the drones that need help are in reach of that chain. [03:28 · simulation 02:05] Normal demand returns; check readiness The disruption has passed. Normal conditions returning is useful, but it does not automatically erase the damage or energy spent during that window. I check the current wing readings before committing again. From here to the finish, the complete run remains visible, including every contact and recovery interval. [05:33 · simulation 05:21] All nine roles connect The mission is complete, and every family has now been introduced: modular hosts, panel grids, reserve carriers, tenders, coordinators, repair craft, scouts, guards, and the battle wing. The next three missions use those same rules with more decisions. Our advantage comes from connecting their work through deliberate priorities and recovery timing. Playback retains the whole simulation chronology. Quiet travel/recovery is labelled at 2× or 4×; narration pauses the replay clock. The positions and results come from the game engine.