After a brief overview of the strategic background and the basic operational situation of Dye's new black-budget R&D team, General Randy paused, turning a piercing gaze directly onto Nick. "I flagged you down to stay behind today partly because the two of us haven't caught up in a long time, so I wanted to seize this window to have a real, off-the-record talk. But on the other hand, I'm also acting as an intermediary for Dye to ask you point-blank: what's your baseline technical assessment of this conversion initiative?
Logically, this program sits way outside your corporate purview, but Dye explicitly told the committee that you're young, highly disruptive, and possess an exceptionally active engineering mind. Moreover, your firm has achieved world-class insights in autonomous swarm-array control technology, zero-visibility high-speed obstacle avoidance, automatic cruising, and tactical AI algorithms. So Dye personally requested that I get your raw, unvarnished thoughts on the project."
Nick offered a slightly bitter smile, shaking his head. Why were they trying to drag him into this defense sector quagmire? As the old industry adage goes, 'don't meddle in procurement cycles outside your paygrade,' and he had zero desire to get entangled in Pentagon politics.
"Honestly, General, I don't really have a formed opinion on the matter. For one thing, I'm completely blind to the classified architecture blueprints of this conversion project, and for another, to be completely candid with you, my firm just isn't commercially interested in this specific vertical."
"Hahahaha, I knew that corporate defensive reflex would kick in the second I asked." Randy poked a playful finger at his shoulder, laughing heartily before adding with an exasperated smirk, "Relax, kid, nobody is drafting you or your company onto the prime contract for this project, so you can drop the corporate filter and just speak your mind."
Nick glanced sideways at Randy , letting out a quiet breath as his shoulders relaxed. To be perfectly honest, he had been harboring a serious amount of corporate anxiety earlier, deeply fearing that Randy was using this scenic tarmac walk as a high-pressure tactic to recruit him into the actual R&D pipeline of this classified program.
He already had a mountain of commercial product launches and enterprise tech deliveries redlining his schedule, and his engineering teams simply couldn't spare a single sprint cycle. But given his tight professional relationships with Randy and Dye, he had been genuinely terrified that a flat refusal would sour their long-term institutional goodwill.
Now, Randy's explicit assurance completely put his mind at ease.
However, as for how to actually formulate an insightful technical critique on the spot, Nick hadn't fully structured his thoughts. The underlying engineering problem was incredibly convoluted, and from a cold, analytical business perspective, he simply wasn't bullish on the project's viability. He was worried that delivering his brutal, data-driven critique would completely deflate the operational confidence of Randy and the entire skunkworks R&D team.
"Go ahead, let it rip. It's just the two of us out here on the concrete, off the record, and I know your character, so whatever technical perspective you throw down stays between us," Randy encouraged, noticing his hesitation and offering a reassuring nod.
Realizing there was no corporate escape hatch left, Nick systematically gathered his technical thoughts, turned to Randy , and said bluntly, "If you want my honest assessment, General, I actually think this entire conversion project is fundamentally dead on arrival."
"Hmm." Randy nodded slowly, his expression entirely unphased by the negative critique, as if he had already anticipated the pushback. He simply pressed, "Break down the engineering logic for me."
"It boils down to three critical bottlenecks: tactical positioning, underlying technology, and life-cycle cost," Nick said, raising three fingers to emphasize the breakdown. "Only by solving for these three variables can this entire program provide any actual utility to the joint chiefs."
"A thoroughly analytical breakdown!" Randy praised, adjusting his stride as they continued down the taxiway line. "Walk me through your data."
Nick kept pace, gesturing toward the masked fighter jets. "First and foremost is definitely the tactical positioning—or rather, the operational objectives and R&D direction of the program. I completely understand the emotional and fiscal argument that it feels like a massive waste to let these flight-capable airframes slowly decay in a desert boneyard, but if we want to remanufacture them for modern warfare, we have to look at the realities of the market. Unmanned combat aerial vehicles?"
Nick shook his head dismissively. "The current threat matrix is completely different from the legacy airspace of the nineties. Our nation's aerospace sector and autonomous drone technology are currently top-tier globally, with almost zero peer adversaries capable of out-engineering our clean-sheet designs. So why would the Pentagon burn valuable engineering hours trying to force modern autonomy into a heavily outdated, legacy aerodynamic platform instead of focusing 100% of our R&D capital on scaling next-gen stealth drone fleets?"
"Are you asserting that these two specific legacy fighter blocks can no longer survive on the modern battlefield?" Randy asked, fixing his gaze on him.
Nick nodded firmly. "Yes, sir. These legacy F-15 and F-16 blocks can only be categorized as late fourth-generation fighters at best. Setting aside their outdated radar cross-sections and structural fatigue limits, their analog fly-by-wire computer architectures and dynamic sensor perception capabilities are decades behind the current threat baseline.
If you try to innovate on top of an inherently obsolete, legacy hardware platform, how much performance can you truly squeeze out of the code? Even if you tried to retrofit fifth-gen avionics and sensors into those old bays, the aerodynamic and power-generation constraints would completely bottleneck the software.
This brings us right back to my first point: what is its actual tactical positioning? A high-performance drone? No matter how many millions you dump into structural modifications, it can never match the low-observable profile, loitering efficiency, or aerodynamic agility of our purpose-built autonomous drone series.
A high-payload suicide strike asset? The massive radar signature and physical size of a legacy fighter mean it will be lit up by adversary integrated air defense networks long before it can match the low-altitude penetration capability or agility of our standard cruise missiles.
And that seamlessly transitions into the third variable: the life-cycle cost. If the per-unit remanufacturing and depot-level modification cost of overhauling one of these legacy fighters turns out to be significantly higher than mass-producing a clean-sheet autonomous drone or a volley of Tomahawk cruise missiles, then the entire program loses all fiscal and strategic justification."
"Your financial and technical logic is incredibly sound, Nicholas. In point of fact, those exact three metrics were the precise battlegrounds where our senior procurement boards and scientific advisors clashed for months before this project ever got its budget line. But do you know the exact strategic calculus that ultimately got this program greenlit by Congress?" Randy asked, his tone turning intensely serious.
Nick shook his head. While he had a few corporate hunches regarding defense-contractor lobbying, he kept them to himself and waited for the officer's internal explanation.
Randy stopped walking, turning to face him with absolute gravity. "Industrial attrition demand. To put it bluntly, son, it's about our strategic reserve capacity for a peer-to-peer conflict.
If a large-scale, high-intensity war breaks out with a near-peer adversary, our intelligence models indicate that our current inventory of cutting-edge, front-line aircraft and precision munitions would likely be completely depleted within the first few weeks of active kinetic engagements. Furthermore, our domestic manufacturing plants, advanced component foundries, and primary logistical supply chains will instantly be prioritized as tier-one kinetic strike targets by enemy long-range assets. When that industrial choke occurs, the Pentagon will have no choice but to activate our deep reserve inventories.
Those mothballed weapons and legacy airframes might not possess the stealth profiles or the advanced computing suites of our active-duty wings, but sheer numerical mass and attritable hulls often play a decisive, war-winning role when the frontline forces are bled dry."
"So this whole program is essentially designed to be an insurance policy—a hidden ace up the sleeve," Nick murmured, the strategic picture clicking into place.
Randy shook his head, a fierce, confident smile flashing across his weathered face. "No, son. We don't want them to be an ace. We want to convert thousands of idle boneyard hulls into an unstoppable royal flush."
Nick felt a sudden chill run down his spine, staring deeply at Randy . The general had claimed that it was Dye who was hunting for technical insights, but the raw intensity in his eyes made it crystal clear that the officer himself was personally and politically invested in the success of this program. This implied Randy's entire career legacy was likely pinned to this black-budget conversion framework.
Realizing the stakes, Nick took a deep, stabilizing breath, shifting his analytical approach. "In that case, General, let's completely table the questions of market positioning and cost-efficiency, and focus strictly on the raw software and mechanical engineering architecture.
From a purely technical standpoint, trying to execute a full-frame modernization on these legacy jets is a fool's errand; the marginal gain in combat effectiveness will never justify the engineering hours. Therefore, my recommendation to Dye's team would be to completely abandon the idea of a comprehensive, bumper-to-bumper airframe modification. Instead, they should focus 100% of their software and hardware integration strictly on the dynamic perception arrays and the fly-by-wire flight control computers.
Or to be even more precise: they should treat this purely as a standardized cockpit capsule modification."
"A cockpit-exclusive capsule modification?" Randy echoed, his eyebrows knitting together in confusion.
"Exactly, a modular cockpit drop-in," Nick nodded rapidly, his voice accelerating as the engineering solution took shape in his mind. "Since this is an entirely unmanned, autonomous combat conversion, the original life-support systems, ejector seats, manual stick assemblies, and physical pilot interfaces become completely useless dead weight.
Removing them instantly reclaims an immense amount of localized space and critical center-of-gravity weight capacity. More importantly, every single primary control loom, avionics bus link, and hydraulic signal line on these legacy fighters already converges directly inside the cockpit tub, making it the absolute ideal, centralized junction box for our hardware modification.
By designing a standardized, self-contained automated control capsule that drops directly into the empty cockpit bay, we can achieve the absolute maximum autonomous flight conversion with the absolute minimum structural alteration and lowest possible per-unit depot cost."
"You're proposing that we build a modular, solid-state electronic processor unit that physically replaces the human pilot's inputs to command the fly-by-wire computers—essentially transforming the vacant cockpit tub into an autonomous, intelligent flight-control brain center?" Randy's eyes lit up with sudden intensity, a massive, triumphant smile instantly breaking across his face.
"Uh, structurally speaking, that's the core engineering thesis, though the actual sensor-bus translation matrix requires a bit more comprehensive mapping..." Nick hesitated slightly, realizing he might have oversold how easy the integration would be.
But Randy completely brushed past the technical caveats. He immediately reached out, grabbing Nick's arm with an excited, iron grip. "Come on, let's get inside out of this wind. I want you to map out every single line of that capsule concept for me right now."
With his free hand, the old general aggressively reached into his heavy uniform coat, pulled out a worn, leather-bound notebook along with a heavy fountain pen, and locked his eyes onto Nick with an expression of intense, undivided engineering expectation.
Nick just stood there, looking at the notebook, realizing he had just coded himself right back into a defense project.