By the time Leo returned to his Pittsburgh office from Houston, it was already the early hours of the morning. The news broke at 3:17 a.m.
CBS’s breaking news banner was the first to flash across the screen, followed by CNN, and then Fox immediately went live. All three networks simultaneously cut to live feeds from reporters stationed near the Pentagon against the backdrop of Washington’s night sky. The anchors maintained a veneer of professional restraint, but their rapid-fire delivery betrayed their underlying excitement.
The US Army had launched a precision strike in the Persian Gulf. The targets were two underground facilities within Iran. The mission was completed in ninety-four minutes, with zero friendly casualties.
At six o’clock the next morning, the Secretary of the Defense Department appeared in the Pentagon’s briefing room. Behind him hung a pull-down screen displaying blurred satellite imagery and operational schematics.
"This operation is a testament to the United States’ military precision strike capabilities, the result of a highly coordinated effort between our intelligence and combat systems."
A reporter raised a hand and asked, "Was AI involved in this operation?"
The Secretary of the Defense Department glanced at the aide beside him before replying, "We utilized all technological means that comply with protocol."
It was neither a denial nor a confirmation. In the subsequent barrage of media questioning, Pentagon spokespersons maintained the same ambiguous stance.
Shortly after the briefing concluded, an article surfaced in a specialized defense technology publication. The author was a veteran contributor with a long track record in Washington circles, and his sources had historically been deemed credible.
The article was titled, "Behind the Ninety-Four Minutes: The Role of AI-Assisted Decision-Making Systems in This Strike Operation."
The piece was written with notable restraint, avoiding sensitive terms like "autonomous weapons." Instead, its phrasing focused heavily on technical aspects: intelligence screening efficiency, target prioritization, and the optimization of logistical coordination pathways. However, reading between the lines made one thing abundantly clear: the AI decision-making assistance system was a core variable in ensuring the operation’s completion within ninety-four minutes with zero casualties.
Within two hours, the article amassed over three million views and was forwarded into the work group chats of nearly every lawmaker on Capitol Hill.
Sarah hadn’t slept since the early hours of the morning. She sat in the monitoring center on the top floor of Pittsburgh City Hall. The three screens in front of her displayed a real-time public opinion heat map, a social media sentiment analysis, and keyword scraping from major news outlets, respectively.
At nine o’clock that morning, the forwarding data for that article fed into her monitoring system. Sarah synchronized the data on all three screens to the latest timeline, rapidly typed in a few search parameters, and studied the results for about five minutes.
Her expertise allowed her to pinpoint critical shifting trends amidst massive datasets in under five minutes. For the past three months, public sentiment regarding the weaponization of AI had maintained a largely negative undertone. This was perfectly reasonable, as media discussions surrounding the topic had heavily concentrated on ethical issues and the risks of losing control.
But ever since the US Army initiated the conflict, the mood had begun to shift. From the early hours of yesterday morning up until now, this sentiment curve had formed a pronounced inflection point.
Voices of opposition were still present, but their overall volume was shrinking. After seeing the result of "ninety-four minutes with zero casualties," the most vocal opponents had notably decreased their output of posts and comments. It wasn’t that they had changed their stance; rather, they had fallen silent. In a public opinion war, silence was sometimes more valuable than opposition, as it stripped the middle ground of its reference points. When the dissenting voices quieted down, the sentiments of moderate voters naturally drifted toward the narrative that the technology was useful and effective.
Sarah took a screenshot of her analysis to archive it, opened a chat window with Leo, and sent a single line: "The time has come."
Leo was already awake and browsing the news reports regarding the incident when he saw the message. He set his phone down, got out of bed, and began to get dressed.
Twenty minutes later, he arrived at the media monitoring center. Sarah was still seated in the same spot, and the data on her three screens had updated to the very latest metrics.
"Talk to me," Leo said, taking a seat in the chair beside her.
Sarah pulled up the data segment showing the inflection point in the sentiment curve. Pointing at the exact timestamp of the shift, she laid out her assessment. Leo stared at the screen, remaining silent for a moment after she finished before finally speaking up.
"How long is this window of opportunity?" he asked.
"Five days to a week," Sarah replied. "The impact of these types of events on public sentiment doesn’t last long. Once the next big news story breaks, or the opposition regroups, this turning point will have passed."
"That’s enough time," Leo said. "Have our media matrix push out the second wave of content starting today. Directly link the direction of Federation procurement with the Pennsylvania Computing Power Special Zone. Place the narrative focus entirely on that."
Sarah jotted this down in her notebook before looking up. "I need an anchor point—an event that the media can cite. If we only rely on our own network of accounts to push this, the spread will be limited."
"I’ll have Ethan pressure Google and Microsoft this morning," Leo said. "If their first move in Washington can land today or tomorrow, that will be our anchor."
Sarah nodded, noting down the coordinated strategy.
"One more thing," Leo added. "Contact Murphy. Tell him to mingle more at the Senate events over the next couple of days. He needs to steer the conversation about the Pennsylvania Computing Power Special Zone toward the Armed Services Committee. He knows what to do."
"Understood," Sarah said. "As for the timeline, I suggest we push out the initial batch of content this afternoon. We should write it from the perspective of local Pennsylvania media, using historical narratives for the headlines. We shouldn’t directly mention national defense—let the readers connect the two dots themselves."
"Good." Leo stood up and cast one final glance over the screens. "You dictate the pacing. If you need any coordination on my end, just let me know."
That afternoon, several local Pennsylvania media outlets simultaneously launched a series of feature articles. The entry point was the history of Pennsylvania’s steel industry, tracing a path from the Pittsburgh steel mills of the early twentieth century, through the conversion of military-industrial production capacity during World War II, all the way to the role the state’s manufacturing sector played in the national defense supply chain during the Cold War.
At the end of these articles, two specific paragraphs were included. The first detailed the current construction progress and projected production capacity of the Pennsylvania Computing Power Special Zone. The second outlined the current geographic distribution of the United States’ computing power resources, highlighting the density gap in the Eastern Region. When placed side by side, readers would naturally connect the logic themselves without anyone needing to spell it out.
Sarah’s monitoring data showed that the local forwarding rate for this batch of content was higher than expected. Furthermore, it spread to other states about forty percent faster than their previous campaign. The breaking news of the "Iran strike" provided a natural emotional backdrop for the topic, making it far easier for the public to consider industrial capacity and national security within the exact same framework.
Meanwhile, Ethan received a call from Google’s business team. David Chen’s lobbying group had successfully booked an appointment that morning with two Chiefs of Staff from the Senate Commerce Committee. The meeting was scheduled for the following day.
Ethan forwarded this news to Leo, who in turn passed it along to Sarah. Sarah marked a new milestone on her media timetable: tomorrow’s second wave of content would be released only after Google’s meeting concluded.
At seven o’clock that evening, the White House held a routine press briefing.
Spokesperson Drew Paxton stood behind the podium, fielding several follow-up questions regarding the Iran operation. His phrasing remained strictly within standard official parlance, offering nothing beyond the scope of the morning’s briefing.
However, just as the briefing was drawing to a close, a reporter raised his hand and asked an off-topic question. "What is the White House’s latest stance on the current capacity building for Federation AI procurement?" he asked.
Paxton paused at the podium for about two seconds before speaking.
"The President believes that the United States’ technological edge must be maintained, and any capability gaps that might threaten this advantage must be bridged as swiftly as possible," Paxton said. "This includes the construction of computing infrastructure, as well as the systematic enhancement of the Federation’s AI application capabilities. This initiative is already underway, and we will update the public on our progress at the appropriate time."
Within fifteen minutes of the briefing’s conclusion, this quote appeared in the push notifications of major tech media outlets. The specific soundbite extracted was: "The AI capability gap must be bridged."
Sitting before her screens, Sarah took a screenshot of the notification, saved it to the day’s public opinion archive, and sent a second message to Leo: "The White House has spoken. Federation procurement has entered the final sprint. Our time window has shrunk a bit more, but we are absolutely on the right track."
Seeing the message in his office, Leo placed his phone back on the desk and stood up to walk over to the window. Outside, the city lights of Pittsburgh bled into the gathering twilight. Things at Three Mile Island needed to be accelerated.
Leo committed this assessment to memory, preparing for his meeting with Evelyn the next day. Outside the window, a gust of wind plastered a few dead leaves against the glass before blowing them away just as quickly. Today was a turning point. Bolstered by today’s news cycle, all their previous groundwork had finally transformed into actionable momentum.
Leo drew the curtains closed, returned to his desk, and picked up the next document. His work wasn’t over yet; there were still many things waiting for him to finish.