Castle deliberated for a long time before ultimately deciding to refuse Mark's request. The stakes were too high. Being caught in the crossfire of three competing defense giants was a precarious position, and a single misstep could result in offending two of them. Taking sides rashly wasn't a risk he could afford to take—it was simply not a wise move.
Just as Castle was about to voice his refusal, the senior vice president, who had been quietly sitting off to the side, spoke up first.
"Mr. Castle, we understand your concerns," the vice president began smoothly. "We also recognize the difficulties you're facing. But perhaps you could approach this from a different angle and consider an alternative solution?"
Intrigued, Castle motioned for him to continue.
"Mr. Castle, the core issue here is that you hold stakes in all three companies, and you don't want to be seen favoring any one of them. After all, if you were to assist one of us, that company would gain a significant advantage in this competition, wouldn't it?
"All three companies now have access to your technology, but turning that into a fully integrated solution remains a challenge for all of us. While manufacturing flexible display panels for aircraft is relatively straightforward, the real difficulty lies in adapting the technology to the specific aerodynamic profiles of the various aircraft we're trying to retrofit."
The vice president then unveiled his suggestion:
"Mr. Castle, have you considered creating a universal template? Or perhaps developing a general modification plan that could temporarily address the obstacles faced by all three companies?
"Of course, this would mean some additional work for you, but it could also resolve the current deadlock.
"Your technology is truly groundbreaking—so advanced, in fact, that even with the resources at our disposal, fully understanding and implementing it will take considerable time. At this point, we finally understand what it means to deal with a true genius. No matter how many engineers we throw at the problem, they simply can't bridge the gap. Many of them even see you as a role model!"
The vice president's words were as crafty as they were persuasive. Not only did he present a seemingly feasible solution to Castle's predicament, but he also flattered Castle with subtle praise, calling him a genius and the idol of their engineers.
Castle, being the self-admitted egotist that he was, couldn't help but feel a twinge of pride at the compliment.
The vice president's approach was calculated and clever. Unlike the technically-minded Mark, who thought in straight lines, the vice president's experience dealing with people shone through. His well-placed praise softened Castle's resistance and nudged him toward considering the proposal.
The suggestion was, in essence, to kick the ball back into Castle's court. While it would require significant effort on Castle's part, it did present a viable solution to his current dilemma.
The primary issue was that all three companies were struggling to fully grasp and implement Castle's technology. On the surface, it seemed straightforward—install flexible display panels on the aircraft's underbelly and wings, then use a high-performance onboard computer, paired with Castle's control program, to blend the aircraft into the sky's background.
In reality, the challenge lay in adapting the technology to different aircraft with vastly differing aerodynamic shapes. Aircraft like the AC-130 gunship, a turboprop transport plane converted into an airborne artillery platform, or the RC-135 electronic reconnaissance plane were relatively easier to modify.
However, Northrop's order to retrofit the B-2 stealth bomber and Boeing's ambitious plans to adapt the technology to the A-10 "Warthog" presented much greater challenges. With their unconventional designs, these aircraft made a "one-size-fits-all" template almost impractical.
Still, Castle had to admit the proposal offered a fresh perspective.
Previously, Castle had avoided the idea of a universal modification template because he doubted its practicality. However, after hearing the vice president's reasoning, he realized that creating such a template could at least mitigate some of the immediate pressure from the three companies.
More importantly, the vice president's comments gave Castle another idea: if all three companies wanted his direct involvement, why not offer his services as a contractor?
Rather than choosing sides, Castle could create custom modification plans for each company's specific aircraft. He could sell these tailored solutions to each company individually, making all three happy—and filling his pockets in the process.
As for who would handle the workload?
Castle had a perfect candidate. His estate's supercomputing lab housed a certain bored, overqualified individual: Harry.
Harry, the perfect assistant, had already helped Castle develop much of the control code for the stealth systems. With the lab's supercomputing power, its vast database, and J.A.R.V.I.S.'s assistance, Harry would have everything he needed to tackle the task.
On top of that, Harry had another key advantage—he was a fully credentialed Northrop Grumman engineer. He had even accompanied Castle to Whiteman Air Force Base in Missouri to assist with the retrofit of the first B-2 stealth bomber.
This gave Harry top-level security clearance and made him an acceptable choice in the eyes of both the military and the three competing companies.
With Harry spearheading the work, Castle's plan to offer custom modification services seemed not only feasible but also highly lucrative.
While Castle mulled over the details of his plan, he played it cool with the Northrop representatives. He told the vice president that he would consider the proposal but politely declined Mark's request to stay at the estate. Citing his own packed schedule, Castle promised to assist remotely instead.
To sweeten the deal, Castle offered to answer Northrop's technical questions via a secure email channel or even conduct video sessions where their engineers could consult him directly.
With J.A.R.V.I.S. safeguarding the communications, Castle had no fear of leaks. But he stood firm on his refusal to let Mark stay at the estate.
Mark, however, was less than pleased. He balked at the idea of using email for such sensitive discussions, concerned about the risks of a security breach. His ultimate goal was to gain full mastery of Castle's technologies, which he believed could only be achieved through direct, in-person guidance.
The vice president, ever the perceptive diplomat, quickly realized why Castle was adamant about not hosting Mark at the estate. Something within the estate—perhaps a secret of great importance—was clearly off-limits. Sensing Castle's reluctance, the vice president tactfully stepped in and dragged the stubborn engineer out before he could push the issue further.
Castle couldn't help but feel a sense of relief and appreciation. The vice president's ability to grasp the unspoken boundaries saved everyone an awkward confrontation.
Once the Northrop team was gone, Castle wasted no time.
He strode into the supercomputing lab, where Harry was engrossed in his latest project, blissfully unaware of the storm heading his way.
Grinning like a wolf spotting an unsuspecting lamb, Castle leaned against the doorway and cheerfully said, "Hey, Harry… I've got a little something for you to do…"
______
(≧◡≦) ♡ Support me and read 20 chapters ahead – patreon.com/Mutter
For every 50 Power Stones, one extra chapter will be released on Saturday.