Three hours after the emergency shutdown, Felix stood in the third-floor conference room at Confluence Logistics, the one they called the war room even before there was a war. The whiteboards had accumulated years of architectural diagrams that nobody ever quite erased—ghosted lines from older systems visible beneath the current ones, like geological strata. The remains of a Primanti's run ringed the table—wax paper smeared with grease, the vinegar smell of coleslaw hanging in the air. Six hours ago those sandwiches had been someone's optimism.
The building's HVAC system cycled on and off at random intervals. It had done this for as long as anyone could remember.
Viktor's question kept circling: What's the right question?
Felix had been asking the wrong ones all morning. How do we fix this? How do we restore the system? How do we catch whoever did this? These were the questions of a man trying to rebuild what had been destroyed. Viktor seemed to be suggesting something else—that the destruction itself was a message, and Felix hadn't learned to read it yet.
The team looked like they'd been through something. Sarah Martinez had stopped fixing her ponytail around hour two; now it listed to one side, and she'd stopped noticing. Dr. Emily Chen had arrived in her running clothes and never changed—her MIT hoodie still damp at the collar, her graying hair pulled back with what looked like a bread tie. She'd been scanning error logs since she walked in, her mouth moving slightly as she read, the way it did when she was working through a problem.
Tommy Rodriguez sat at the far end of the table, hands wrapped around a mug of coffee that had gone cold two hours ago. Twenty-five years of gripping a steering wheel had left the knuckles permanently swollen. When Tommy spoke in meetings, keyboards stopped clicking.
Maria Santos sat closest to the door, legal pad already half-filled with notes in handwriting only she could read. She'd been organizing workers for thirty-two years. Her pen moved constantly.
Sarah glanced at the moving pen. "You know we have the AI notetaker running, right?"
"I know." Maria didn't look up. "The machine captures what was said. I capture what it meant."
"Alright." Felix pushed himself up from the table. His knee had locked during the hours of sitting; he had to take two steps before it would bend properly. He made it to the whiteboard without limping, mostly. "Let's start from the beginning. Sarah, walk us through what we know."
Sarah pulled up a network diagram on the main screen. "The attack targeted three layers simultaneously—attention mechanisms, long-term memory, and trust protocols. Everything that lets the system decide what matters, remember what it's learned, and verify what it's told."
"The CAP theorem parallel you mentioned earlier," Emily said, nodding. "Context, Memory, Trust. They took all three."
"Exactly. But here's what's interesting." Sarah highlighted a section of the logs. "They didn't attack us directly. They went after our upstream data sources."
She pulled up a pipeline architecture diagram. "We aggregate data from hundreds of sources—traffic APIs, weather services, customer databases, third-party logistics providers. The attackers compromised several of these upstream sources, embedding prompt injections in what looked like normal data fields."
"Like hiding poison in the ingredients before they even reach the kitchen," Tommy observed.
"Could be hardware degradation," the overnight technician suggested from the doorway. He'd been running diagnostics since 4 AM. "Memory errors could explain the drift."
"Hardware's clean," Sarah said. "And network latency would cause random errors."
Felix shook his head. "This is systematic. Look at the direction." He traced the pattern on the screen. "Every decision is drifting the same way. That's not noise. That's signal."
The room went quiet as the implication settled in. Not a malfunction. Not an accident. Someone was teaching their system to fail.
Emily leaned forward. "The injections were buried in normal data—hidden instructions in weather reports, commands embedded in traffic feeds. Each one subtle. Together, they caused our models to gradually forget their training."
"Catastrophic forgetting," Sarah said. "When new patterns overwhelm the training, the model loses everything it learned."
Tommy's face changed. "Catastrophic forgetting... like what happened to Iron Mike Webster?"
In Pittsburgh, you didn't have to explain who Webster was. The legendary Steelers center, four Super Bowl rings, played through hits that would have ended other careers. The CTE had taken him apart piece by piece—first his memory, then his judgment, then whatever was left.
"That's exactly right," Emily said quietly. "Webster took 25,000 hits, each one small, cumulatively rewiring his brain. Our AI experienced the same thing—thousands of prompt injections through our data feeds, gradually making the system forget its core training. The safeguards we built to protect workers got erased first."
Tommy nodded slowly. "So someone taught it to forget the parts that mattered to us."
"And once it started forgetting—"
"It kept forgetting." Tommy's face was grim.
Maria looked up from her notes. "Every hour our network is down, we're not just losing theoretical coordination benefits. We're talking about 400 medical supply deliveries that won't reach hospitals on time. About 5,000 small businesses that can't get their inventory. Real money—about $500,000 per hour in delayed shipments and penalties."
"And one NICU in Milwaukee," Felix added quietly, "waiting on supplies that aren't coming."
Tommy shook his head in frustration. "This is exactly what we were afraid of when we started this project. That someone would find a way to turn our own tools against us."
"What about our observability systems?" Felix asked. "Why didn't we catch this data poisoning earlier?"
Sarah grimaced. "That's another part of the problem. The attack included sophisticated techniques to evade our observability measures. The poisoned data was designed to produce outputs that looked normal to our automated monitoring systems."
She pulled up a decision log. "Look at this one. The AI chose a technically efficient route that required Jim Patterson to work a fourteen-hour day with minimal breaks. Three kids, coaches Little League—the system knew all this and ignored it. And when our human-in-the-loop flagged it, the poisoned metadata created false urgency—'critical medical supplies,' 'time-sensitive pharmaceuticals'—to get our own reviewers to wave it through."
Maria Santos leaned back in her chair. "So they didn't just poison our data. They manipulated our people too."
What's the right question?
Viktor's voice echoed in Felix's mind. He'd been asking how to defend the system. But maybe that was like asking how to prevent CTE by giving players better helmets. The helmets helped, but they didn't address the fundamental problem—the game itself made brain damage inevitable.
"We need to think about this differently," Felix said, walking to the whiteboard. He wrote Viktor's words at the top: The attack is the symptom. The problem is the design.
"What does that mean?" Maria asked.
"I'm not entirely sure yet." Felix stared at the words. "But I think we've been asking the wrong questions. We've been asking how they got in, how we can keep them out, how we can restore what we had. But maybe the fact that they could do this—that our system was vulnerable to this kind of attack at all—means there's something fundamentally wrong with how we built it."
Emily's eyes narrowed. "You're saying the vulnerability isn't a bug. It's a feature we didn't realize we'd included."
"The system was too centralized," Sarah said slowly, following the thread. "We built trust hierarchies. Aggregation nodes that validated data before distribution. Attention mechanisms that weighted certain inputs over others. Those were all points that could be corrupted."
"We built a symphony," Felix said, the words coming slowly as the idea took shape. Something Viktor had implied on the phone—or maybe something Felix was only now hearing. "With a conductor who could be compromised. Every hierarchical system has this problem. The more control you concentrate, the more valuable that control becomes to attackers."
Tommy leaned forward. "So what's the alternative? No conductor at all? That's chaos."
"No," Felix said. "Not chaos. Jazz."
Felix wasn't entirely sure what he meant by it—the insight was still forming, still incomplete. But something had shifted in how he was seeing the problem. They hadn't just been attacked. They'd been shown something about themselves they hadn't wanted to see.
"Jazz," Maria repeated skeptically.
"I'm meeting someone tonight who might be able to explain it better than I can." Felix glanced at his phone. It was already past noon; the jazz club meeting was less than seven hours away. "Someone who's been through this before—built something, watched it get corrupted, walked away."
"Who?" Emily asked.
"His name is Viktor Antonov. Built a voice recognition platform, watched the acquiring company gut everything democratic about it, walked away." Felix paused. "He's been asking me the questions I don't want to answer for six years."
Tommy's expression shifted from skeptical to interested. "And he thinks he knows what we did wrong?"
"He thinks I don't know what question to ask yet." Felix capped his marker and set it down. "He might be right."
Maria stood, gathering her legal pad. "So what do we do in the meantime? We've got two hundred companies depending on a network that's down, union reps calling every ten minutes, and city officials who want answers we don't have."
"We keep analyzing the attack," Felix said. "Document everything. Trace every injection point, every compromised data source. Not just to understand how they got in, but to understand what our architecture assumed that turned out to be wrong."
He looked around the room at his exhausted, worried team. "And we start thinking about what a different kind of system would look like. One that doesn't have a conductor to corrupt. One where the music keeps playing even when individual players get compromised."
"You really think that's possible?" Sarah asked.
"I don't know. But I think Viktor might. And I think he's going to make me figure it out for myself rather than just telling me." Felix managed a tired smile. "Apparently that's how he teaches."
Tommy set down the cold mug and stood. "I've got about forty drivers who are sitting at home wondering if they still have jobs. I should go talk to them, let them know what's happening. The union meeting is at four."
"Tell them the truth," Felix said. "We were attacked. We're figuring out how. And we're going to build something better—something they'll have a real voice in designing."
"They'll want to know how long the network will be down."
Felix hesitated. The honest answer was that he didn't know—couldn't know, until he understood what "rebuilding" actually meant. "Tell them we're working on it. And tell them that when we bring it back, it's going to be different. Better. More theirs."
Tommy nodded slowly. "I can sell that. For a little while, anyway. But Felix—these folks have been promised 'better' before. By a lot of people who didn't deliver."
"I know." Felix thought of his father in the kitchen on the day the company folded, hands shaking around a coffee cup, shoulders curved forward like he was still behind a wheel that wasn't there anymore. "I know exactly how that feels."
After the team dispersed, Felix pulled out his phone and looked at Viktor's message again.
Don't bring your laptop. Bring your questions.
The laptop would give him answers. But answers weren't what he needed. Not yet.
The jazz club on Liberty Avenue. Seven PM. Felix pocketed the phone and walked out.