The night in Mountain View was still.
The lights at Google Park were still on, but the hallways were mostly empty. The only people left were those who treated the company as their home.
David Chen, Vice President of Google Infrastructure, sat in his office with two screens in front of him. One displayed the real-time after-hours stock price curve, while the other showed a press release just published by a competitor. The press release was plainly worded, but every sentence perfectly hit the needs of the Federation Procurement Committee.
"Our system design prioritizes national security without functional limitations.
"Our team has completed the Federation security clearance and is ready for technical review by the procurement department at any time.
"We understand that in an era of strategic competition for the nation, the responsibility of technology companies is to serve, not to set boundaries."
David read the article from beginning to end twice before pushing the screen away. He had been at Google for eleven years, overseeing the global layout of data center infrastructure. This job had exposed him to all kinds of competition: price wars, technology wars, and PR wars. But for the first time, he felt a completely different kind of pressure.
The competitor was using compliance as a weapon, turning Google’s prudence into a political target. The Anthropic incident had already spread through the industry yesterday. Negotiations for the national defense version of Claude had broken down for a simple reason: they refused to hand over completely autonomous weapon decision-making power to the military, and they refused to open up the control logic of large-scale surveillance infrastructure.
The people at the Pentagon used one term: supply chain risk. The lethality of this term was greater than any technical review. Because it wasn’t about capability; it was about loyalty.
David stared at the downward stock price curve, then pulled up another document detailing the framework requirements for the construction of "national security-grade data centers." In terms of AI capability, Google was confident it wouldn’t lose to any competitor in the world. But looking at the complex clauses in the document, David felt a headache coming on. These requirements went beyond the realm of pure technology; they involved land, energy, law, and even geopolitics.
David did a simple math problem in his head. The scale of this Federation AI unified procurement was confidential, but industry estimates ranged between thirty to fifty billion US Dollars, with a ten-year contract term and a priority renewal clause included. Winning this order meant Google would have the power to define the Federation AI market for the next ten years. Failing to win it meant competitors could use this admission ticket to slowly squeeze Google out of the market.
He picked up his phone and sent a message to the Director of Federation Business: "6:00 AM tomorrow, conference room." Then, he reopened the infrastructure map and began studying the distribution of data centers in the Eastern United States.
At the same time, it was already 2:00 AM in Seattle.
Microsoft’s Federation Business team was still online. The seventeen people were scattered across different time zones, and everyone on the video conference screen sported dark circles under their eyes. Hosting the meeting was the Vice President of Federation Business, Diane Faulkner. She pinned a screenshot of a key paragraph from an internal assessment report onto the shared whiteboard. The conclusion of the assessment report was brief: If Google was the first to complete the delivery and acceptance of a national security-grade data center, Microsoft would lose the initiative in the Federation AI procurement track for the next three years.
"I know everyone is tired right now," Faulkner said directly, "but this matter cannot wait until Monday."
Someone asked, "We have no issues on the technical level. Where is the problem?"
Faulkner wrote three phrases on the whiteboard: Verifiable Computing Power, Auditable Energy, and Traceable Data. "The Federation requires these three conditions to form a closed loop in the same geographical location," she explained. "California’s power grid is too fragile, Texas’s independent grid has had incidents, and the data centers in Virginia are already too concentrated, which has triggered decentralization requirements."
Silence fell over the virtual conference room for a few seconds.
The engineer in charge of site selection spoke up first. He shared his screen, displaying a map of the United States with several eastern states highlighted in different colors. "Pennsylvania," he said. "More specifically, the industrial belt in western Pittsburgh."
Faulkner looked at the location and called out Leo Wallace’s name.
"The Computing Power Special Zone," someone chimed in. "He’s been pushing this all along, but the energy side has been stalled. Coupled with the energy suppliers interfering with the restart of Three Mile Island, we did an internal evaluation and decided not to follow up because the timeline for implementation was too uncertain."
"When was that judgment made?" Faulkner asked.
"A month ago, maybe several months? I can’t remember clearly."
"The situation is different now." Faulkner closed the map and switched the screen back to the assessment report. "Previously, this was a low priority because we had other paths to take. Now, this is the only path." She checked the time. It was 2:10 AM. "Contact Leo’s team and arrange a meeting. The sooner, the better."
By the time David Chen’s 6:00 AM meeting concluded, it was almost eight o’clock.
The conclusion in their conference room was nearly identical to Faulkner’s. California, Texas, and Arizona were eliminated one by one, leaving only Pennsylvania. The Computing Power Special Zone project had previously dropped off the priority list for Google’s Federation Business, and Leo’s team hadn’t taken the initiative to contact them again, leaving the matter shelved between both parties. Google’s own judgment was that the Three Mile Island situation was too troublesome; the Nuclear Regulatory Commission’s approval process easily took five years or more, and they couldn’t afford to wait. But now, what they couldn’t afford to wait on was something else entirely.
"The problem with Three Mile Island is still there," David said. "But that’s Leo’s problem. He has to solve it, and we will cooperate. We only have one question to ask: Can he give us a definitive timeline?"
Someone said, "His entire industrial mobilization system in Pittsburgh is already up and running. If he really makes up his mind to do this, theoretically, he has the execution capability."
"Then let’s go talk to him." David stood up. "I’ll go in person."
In Pittsburgh, Ethan received the first phone call. It was from an intermediary on Google’s business team, speaking very politely. They said David Chen hoped to arrange a face-to-face meeting as soon as possible to discuss the advancement of the Computing Power Special Zone. Ethan hung up and called Leo.
"Google wants to meet with you."
Leo was in his office, reviewing a report on the grid capacity of Western Pennsylvania. When Ethan’s call came in, he didn’t even lift his head. "When?"
"They said the sooner the better. They can come to Pittsburgh this week."
"Alright, arrange it."
Leo put down the report and leaned back in his chair. He had long expected Google to come. During the two days of the hearings, he had been watching the news. Anthropic had been singled out for criticism, their moral red lines translated into supply chain risks. Once this characterization was established, all the tech companies looking to snag a massive Federation order would make a move, and Google and Microsoft would definitely be in the first wave. When looking for a place to establish a national defense data center, they would undoubtedly seek a state with stable electricity that could pass Federation security audits. Right now, Pennsylvania was the only option.
The Computing Power Special Zone project had been stalled ever since the signing ceremony. Problems arose on the energy side, progress on Three Mile Island was repeatedly delayed, and Constellation Energy showed no intention of making a move. The people from Google and Microsoft had faded into the background, and Leo hadn’t proactively pushed them. But the situation had changed. Google was coming to Leo because they were anxious.
Leo recalculated this variable in his mind. He had stared at the location of Three Mile Island entirely too many times. That area was just a tiny coordinate on the map, but the chain it affected linked the Energy Association, Constellation Energy, the Nuclear Regulatory Commission, and Congressmen all together. If Google could translate the delivery requirements of this Federation order into a political endorsement for Leo, the resistance along that chain would be vastly reduced. Because it would no longer just be a Mayor pushing his industrial revival plan. It would be Federation defense procurement pointing toward Pennsylvania. If Constellation Energy continued to stall, they wouldn’t just be blocking Leo—they’d be blocking the AI strategic layout of the entire Federation. With that label slapped on them, no one could avoid the consequences.
Ethan pushed the door open and walked in, holding a tablet. On the screen were two news items from this morning. "Microsoft has also sent a meeting request," he said. "They want the exact same timeframe as Google—this week as well."
Leo took the tablet and glanced over it.
"Schedule them for the same day."
Ethan looked up at him. "You want them to know the other side is coming too?"
"Of course." Leo handed the tablet back. "They won’t know each other’s trump cards, but they will guess, and that’s enough."
Ethan made a note on the tablet, then raised his head. "Should we give Sterling a heads-up in advance?"
Leo thought for a second and shook his head. "Wait until the people from Google and Microsoft arrive. After I negotiate the terms clearly with them, I’ll go to Sterling. My hand of cards will be much stronger then."
That afternoon, Google’s itinerary was finalized.
David Chen and two members of his team booked early Wednesday flights to Pittsburgh. The trip was only for one day—flying in and flying out on the same day. On Microsoft’s side, Faulkner dispatched the Federation Business landing team. The three-person team would arrive in Pittsburgh on Wednesday morning and fly back to Seattle on Thursday morning.
At night, most of the lights in the Mountain View park had gone out. Before leaving, David Chen took one last look at the map. The location of Pennsylvania had been marked in red by him, with a single word noted beside it: Wait.
Over in Seattle, Faulkner was already in bed, but her phone was on. The chime of email notifications rang every few minutes.
Two planes took off.
One from San Francisco, one from Seattle. Both bound for Pittsburgh.