After returning to Tampa, Nick originally gave Terry a week off to decompress. Unexpectedly, the very next morning, the guy came bouncing into the office, tracked him down, and excitedly started buzzing about their next project.
Nick led him to the Swarm-Array Control Technology lab on the third floor, smiling as he spoke. "Do you remember back in Miami, when you used your FPV racing drone to intentionally ram that surveillance drone to stop it, and it ended up crashing into the river?"
"Boss, you still remember that?" Terry was caught off guard. It had been almost a year since that afternoon, and he didn't expect Nick to keep track of a broken hobby drone. The gesture hit him right in the chest.
In reality, the moments that truly stick with us aren't always grand, sweeping spectacles. Often, it's the granular details of a specific event—a single sentence or a memory shared between friends.
"Of course I remember. I told you back then I'd hook you up with a better one," Nick said with a grin.
Terry shook his head. "No need, Boss. I can just scratch-build a new racer myself."
"Then you can handle the manufacturing yourself. I've already laid out all the components for you," Nick said, gesturing toward the workstations in the center of the lab.
"Holy crap... that's a lot of quadcopters!"
Terry followed his gaze and saw rows of matte-black FPV drones, each roughly the size of an adult's palm, lined up across the main testing bench. There had to be dozens of them. In the surrounding workstations, various airframe designs were on display, and several engineers were actively running diagnostic software.
"Mr. Harrison!"
A young engineer, probably twenty-six or twenty-seven, walked over. Seeing Terry, his face lit up. "Doctor Terry! Man, you didn't waste any time getting back into the lab."
The speaker was Mike Harris, the assistant lab manager and another veteran of the early Miami tech deployment. While Terry was buried at the Amazon hub, Nick had temporarily placed Mike in charge of the Swarm-Array core flight team.
As for the title "Doctor Terry," it was essentially shorthand for Director of Systems Architecture within the lab. Of course, it was a secondary leadership role; Nick retained the executive director title and personally steered the research direction, while Terry and Zack held co-director slots. In practice, they were just internal titles meant to streamline the chain of command.
Terry nodded to Mike, his eyes darting across the bustling technicians before he turned back to Nick. "Boss, is this the black-budget project you were talking about?"
"How about it? Look like a good sandbox?" Nick asked with a smile.
"Incredible. This is exactly my kind of sandbox." Terry was beaming as he walked over to the bench, picking up an unmapped airframe to inspect the carbon-fiber chassis.
"The center of gravity and motor placement are completely different from a standard racing quad." Terry rotated the frame, studying the battery mount before looking up at Nick. "Alright, Boss, quit teasing. What's the mission profile for this thing?"
"We call it the Sweeper."
Nick smiled and hit a button on his tablet, waking up the massive wall monitor. A simulated tactical feed flashed onto the screen, showing a high-speed cloud of micro-drones tracking down and neutralizing hostile combatants sprinting through a mock urban environment.
At the top of the feed, bold, digital-camouflage text read: Project Battlefield Sweeper.
Seeing the tactical layout, the puzzle pieces finally clicked together in Terry's mind. But as the engineering implications sank in, his brow furrowed. "Boss, I'm a little confused. How is this fundamentally different from the Swarm Attack configuration we engineered for the Air Force Research Lab?"
"The underlying Swarm-Array architecture is identical," Nick agreed, nodding. "The difference lies entirely in the target acquisition and tactical deployment. The 'Killer Bee' heavy swarm platform was engineered to suppress large-scale anti-air emplacements, armored columns, missile batteries, and command bunkers during theater-level engagements."
"The Battlefield Sweeper—formally known as the Tactical Swarm Precision Strike System—is built for micro-targeting. We're hunting infantry squads, machine-gun nests, mortar positions, sniper teams, and light technicals entrenched in defensive perimeters. Its primary environment is complex, non-linear terrain—specifically urban close-quarters combat and dense jungle operations."
"Under traditional doctrine," Nick continued, mapping out a battle line on the screen, "an offensive starts with a massive artillery barrage or an airstrike, followed by light infantry moving in to clear the remaining resistance. The problem is that heavy kinetic ordnance is incredibly inefficient at clearing combatants dug deep into concrete basements, subway systems, or triple-canopy jungles."
"Heavy armor like main battle tanks can't maneuver in those tight, debris-choked environments, which completely neutralizes their combat effectiveness. That forces commanders to send fire teams in on foot to clear structures room by room."
"As we know from history, urban operations and jungle ambushes are absolute meat grinders. The moment our infantry crosses that threshold, they are highly vulnerable to IEDs, crossfire, and surprise counter-attacks.
Once friendly and hostile forces are intermingled in a single city block, calling in close air support becomes an absolute nightmare. A disciplined enemy can leverage the rubble to play cat-and-mouse with our squads, bleeding us out through attrition. The casualties in those scenarios are historically devastating—just look at the military's past urban campaigns."
Nick paused, setting down his tablet to pick up one of the palm-sized prototypes.
"The Sweeper was engineered specifically to solve the urban infantry dilemma. The entire system is lightweight—dozens of times lighter than a standard Javelin missile or an AT4 rocket. An individual operator can carry a deployment pod in a rucksack or mount a multi-tube launcher to the back of a Joint Light Tactical Vehicle."
"When a squad takes fire, they can deploy a single unit, a fire team element, or an entire autonomous swarm. The soldiers just punch the launch command, and the drones automatically network together, divide up the target sector, map the interior of the structures, and eliminate hostile threats before our boots ever cross the fatal shore."
Terry listened intently, but his expression remained skeptical. "FPV platforms have the kinetic speed needed for rapid intercept, which makes them great for kinetic strikes. But that velocity makes them incredibly unforgiving to fly. The battlefield is a chaotic environment, especially inside blown-out concrete buildings or thick forest cover. Keeping a quadcopter from clipping a branch or a jagged piece of rebar at ninety miles an hour is nearly impossible."
"Unless you have a tier-one drone racer at the sticks for every single unit, it's going to crash before it finds a target," Terry pointed out, highlighting the engineering bottleneck.
Nick's smile only widened. "Exactly. And that's the engineering bottleneck we need your brain to solve."
"Out of everyone on the payroll, you understand the kinetic physics and flight boundaries of high-speed quads better than anyone. That's exactly why I flew down to Miami to yank you out of that warehouse. I need you to lead the flight-automation integration."
Terry frowned, staring down at the sleek black drone in his hand. After a long, silent moment of calculating the variables, he looked up at Nick. "I'm not going to lie to you, Boss. The collision-avoidance math at those velocities is brutal. I can't promise a silver bullet, but I'll throw everything I've got at the code."