Miles had been staring at the same data visualization for three hours when he saw it.

  "Jax," he said without looking up from his interface. "Come look at this."

  Jax moved from his desk to stand behind Miles's chair, silent as always, and waited.

  "Seventeen crimes orchestrated by The Conductor over the last three months," Miles said while highlighting patterns on his holographic display. "Look at the timestamps."

  The data hung in the air: seventeen operations, seventeen locations, seventeen different objectives.

  But one thing was identical across all seventeen.

  "1734 hours," Jax said.

  "Every single time," Miles confirmed. "Not approximately 1734, not between 1730 and 1740, but exactly 1734. Peak Surge begins at 1733 and reaches maximum gridlock at 1734. The Conductor times every operation to the minute when traffic is most catastrophic."

  "That's not coincidence."

  "That's deliberate strategy." Miles pulled up traffic flow data and overlaid it with the crime locations. "And look at where he strikes—not random locations but specific junctions where gridlock creates natural chokepoints and where emergency response is slowest."

  Jax studied the patterns. "Each crime location is positioned at intersection with maximum distance from nearest police station during Peak Surge conditions."

  "He's using the traffic algorithm against us." Miles expanded the visualization to show response times. "Average police response to these seventeen crimes was seventy-three minutes because we're trapped in the same gridlock as everyone else. By the time we arrive, his operatives are gone and evidence is minimal."

  "This is sophisticated operational planning."

  "This is someone who understands the traffic system better than the people running it." Miles highlighted another pattern. "But here's what's interesting—none of these crimes actually hurt anyone. No casualties, no injuries, minimal property damage. They're designed to be visible and dramatic and impossible to ignore, but not violent."

  "What's the objective if not violence or profit?"

  Miles pulled up media coverage of each incident. "Public attention. Every operation generated major news coverage and social media discussion and political pressure on TMA. The Conductor isn't trying to terrorize people or steal money—he's trying to expose how broken the system is."

  Jax sat down and pulled up his own interface. "If The Conductor's goal is system exposure, then each crime should target specific vulnerability or demonstrate specific flaw."

  "Let me check." Miles cross-referenced each crime with its tactical outcome. "Operation One: data theft from traffic server farm. Media coverage focused on how TMA's security was insufficient. Operation Two: coordinated vehicle blockage at major intersection. Media coverage focused on how emergency vehicles couldn't respond during gridlock. Operation Three—"

  "Each operation demonstrates different system failure," Jax interrupted. "This isn't random criminal activity. This is systematic vulnerability demonstration."

  "This is engineering methodology," Miles said slowly. "The Conductor isn't thinking like a criminal, he's thinking like an engineer testing system weakness."

  "If Dr. Adrian Cross is The Conductor, then he's using engineering approach to expose system he helped create."

  They sat in silence for a moment, processing the implications.

  "We've been investigating this wrong," Miles said. "We've been treating The Conductor as criminal mastermind orchestrating heists, but he's actually conducting system analysis through live demonstration."

  "The crimes are experiments," Jax said.

  "The crimes are proof-of-concept operations showing exactly how TMA can manipulate traffic and exactly how vulnerable the city is to that manipulation."

  Miles pulled up the case files they'd been building. "If we're right, then The Conductor's next operation should target a new vulnerability—something he hasn't demonstrated yet."

  "What vulnerabilities remain?"

  "Let me check what he's already covered." Miles listed them: security failures, emergency response delays, priority routing, system manipulation, traffic prediction, data accessibility. "He hasn't demonstrated direct harm to specific populations or targeted elimination of individuals using traffic control."

  "That would require proving TMA can kill people deliberately through algorithm manipulation."

  "That would require proving what killed your family."

  Jax's expression didn't change but something shifted in his eyes.

  Miles kept working. "If The Conductor follows his pattern, his next operation will demonstrate that TMA's algorithm can be weaponized to cause fatalities. That's the final piece of evidence needed to prove systematic murder."

  "When?"

  "Today at 1734 hours." Miles checked his chronometer. "Three hours from now. We need to figure out where and stop it before it happens."

  "Stop it how? We don't know target location and we don't know intended method."

  "We use the same methodology The Conductor uses—we analyze the system and predict vulnerability." Miles pulled up current traffic patterns and infrastructure data. "Where would you stage an operation to demonstrate algorithmic murder?"

  Jax thought for thirty seconds. "Location would need high-value target, guaranteed gridlock, medical emergency requiring rapid response, and system control sufficient to prevent that response. Medical emergency during Peak Surge with blocked ambulance access would prove algorithm can kill deliberately."

  "So we're looking for hospitals or medical facilities near gridlock-prone junctions." Miles filtered the map. "That's still seventeen possible locations."

  "Narrow further. Operation must be dramatic enough for media coverage and shocking enough for public outrage. High-profile target."

  "Brightside Children's Hospital at Junction 31," Miles said immediately. "Major pediatric facility, always traffic-adjacent, serves high-sympathy population. If The Conductor stages medical emergency there and demonstrates that TMA's algorithm prevents ambulance response, public outrage would be massive."

  "That's speculation."

  "That's engineering prediction based on pattern analysis." Miles stood up. "We need to tell Captain Reyes."

  They found Reyes in her office, interface buffering as always, and presented their analysis.

  "Let me understand your theory," Reyes said after listening to their explanation. "You believe The Conductor will stage a fake medical emergency at Brightside Children's Hospital during Peak Surge to demonstrate that TMA's algorithm can kill people deliberately through traffic manipulation?"

  "Yes," Miles said.

  "Based on pattern analysis of seventeen previous crimes and operational methodology assessment?"

  "Yes."

  "And you want authorization to stake out Brightside for the next three hours on the theory that major crime will occur at exactly 1734?"

  "Yes."

  Reyes's interface crashed completely.

  You might be reading a pirated copy. Look for the official release to support the author.

  She rebooted it manually and looked at them with exhausted patience. "Even if your theory is correct—which is generous assumption—I cannot authorize stakeout based on speculation. I already ordered you to focus on street-level crime and stop investigating The Conductor."

  "But Captain—" Miles started.

  "That order still stands." She looked at them meaningfully. "However, if two detectives happened to be in the area of Brightside on their lunch break at 1734 hours, I cannot control where they eat lunch. Do you understand?"

  "We understand," Jax said.

  "Good. Get out of my office and go eat lunch somewhere that might coincidentally position you to respond to theoretical crimes that definitely won't happen."

  They left quickly.

  At 1423 hours, they were positioned near Brightside Children's Hospital with clear sightline to main entrance and emergency access routes.

  Miles had his interface monitoring traffic patterns and communication networks and security feeds. Jax had his weapon ready and his augmented reflexes primed.

  "This might be wrong theory," Miles said while they waited.

  "Theory is based on sound analysis."

  "Theory is based on speculation and hope and desperation to stop something that might not happen."

  "Theory is only strategy we have."

  They watched traffic build toward Peak Surge. Standard gridlock formation—vehicles clustering, routes constricting, emergency lanes filling with civilian traffic.

  At 1647 hours, Miles noticed something unusual.

  "Ambulance routes near Brightside are showing pre-gridlock congestion," he said while checking traffic data. "That's almost an hour before Peak Surge actually starts."

  "Natural congestion or artificial congestion?"

  "Checking algorithm activity..." Miles dove into traffic management data through questionably legal access methods. "This is artificial. The algorithm is routing additional traffic toward ambulance access points deliberately."

  "The Conductor is setting the stage."

  "Or TMA is creating problem for unrelated reasons."

  "Or both."

  At 1718 hours, traffic around Brightside reached complete saturation. Every route was blocked, every lane was full, and emergency vehicles would need minimum forty-three minutes to reach the hospital from any direction.

  At 1729 hours, Miles's interface detected encrypted communication burst near the hospital—short, untraceable, directed at unknown recipient.

  "Something's happening," Miles said.

  "What something?"

  "Unknown something but definitely something because that encrypted burst matches signature from previous Conductor operations."

  At 1734 hours exactly, emergency alarm activated at Brightside Children's Hospital.

  Miles's interface immediately picked up dispatch: "All units, medical emergency at Brightside Children's Hospital, critical patient requires immediate ambulance transport to surgical facility, nearest ambulance ETA unknown due to traffic conditions."

  "It's happening," Miles said. "Medical emergency exactly as predicted."

  "Is emergency real or staged?"

  "Checking hospital systems..." Miles accessed Brightside's network through creative authentication. "Patient is real—twelve-year-old with ruptured appendix requiring emergency surgery. Hospital can't perform surgery, needs transport to General Hospital surgical unit."

  "That's real emergency, not staged."

  "That's real emergency that The Conductor predicted and allowed to happen to demonstrate system failure."

  "Can we get ambulance through?"

  Miles checked traffic patterns. "Not through normal routes—gridlock is complete and algorithm isn't allowing emergency override. Ambulance is stuck seventeen blocks away and isn't moving."

  "Then we transport patient ourselves."

  "In what vehicle? Your motorcycle can't carry medical patient."

  "We take hospital ambulance and I drive using emergency protocols."

  "You're not certified ambulance driver."

  "I am certified emergency responder and circumstances require adaptation."

  They ran to hospital entrance where staff were frantically trying to coordinate transport while gridlock prevented all normal emergency response.

  "GLPD," Jax said while showing his badge to the charge nurse. "We can transport patient using alternative routing."

  "You're not ambulance crew," the nurse said.

  "We are available responders and patient will die without transport. Load patient now."

  The nurse made decision in three seconds. "Bay Seven. Stable for transport but needs surgery within ninety minutes."

  They loaded into ambulance with patient—twelve-year-old girl named Sophie, conscious but in pain—and two medical staff.

  Miles jumped in driver seat. "I'm driving because Jax navigates."

  "You're terrible driver," Jax objected.

  "I'm adequate driver with excellent navigation support. You tell me where to go and I'll get us there."

  They pulled out of hospital bay into complete gridlock with emergency lights activated and sirens blaring and traffic that absolutely refused to move because traffic couldn't move.

  "This is impossible," one of the medical staff said. "We're stuck like everyone else."

  "Not stuck," Miles corrected. "Just not using standard routes." He turned to Jax. "Navigate."

  Jax pulled up his interface and accessed the city's infrastructure map—not traffic routes but service corridors and maintenance access and emergency channels that weren't controlled by TMA's algorithm.

  "Right turn next intersection, use bus lane," Jax directed.

  Miles turned into bus lane—illegal but necessary—and accelerated through gap that normal vehicles couldn't access.

  "Left turn at Junction 23, use delivery corridor behind commercial district."

  "That's not a road."

  "That's a viable path. Use it."

  Miles turned into what was essentially an alley but was technically wide enough for ambulance if nobody cared about mirrors or paint jobs.

  They scraped through with centimeters to spare.

  "This is insane," the medical staff said.

  "This is effective," Miles countered while following Jax's navigation through the city's hidden infrastructure.

  Behind them, stuck in gridlock seventeen blocks away, the official ambulance wasn't moving.

  Ahead, General Hospital surgical unit was waiting.

  At 1847 hours—seventy-three minutes after the emergency call—they delivered Sophie to surgical unit successfully.

  "You just saved her life," the medical staff said while unloading.

  "We just proved the system is designed to kill people," Miles corrected.

  While Sophie was being prepped for surgery, Miles and Jax stood in the hospital parking area and reviewed what had happened.

  "The Conductor predicted this emergency," Miles said.

  "The Conductor created conditions for this emergency by manipulating traffic to block standard response," Jax said.

  "But we stopped it by using alternative routing that TMA doesn't control."

  "We proved that system can be bypassed but also proved that system is designed to prevent emergency response."

  Miles pulled up his interface where his livestream had been recording everything—fifty-three thousand viewers had watched the entire emergency transport.

  His interface chimed with new message from encrypted source: WELL DONE. YOU PREDICTED MY OPERATION AND PREVENTED THE INTENDED OUTCOME. THE PATIENT SURVIVES BECAUSE OF YOUR INTERVENTION. BUT YOU ALSO PROVED MY POINT—TMA'S ALGORITHM WOULD HAVE KILLED HER. OFFICIAL AMBULANCE IS STILL STUCK IN GRIDLOCK. YOU SAVED ONE LIFE. HOW MANY OTHER LIVES HAS THE ALGORITHM TAKEN WHEN NO ONE WAS WATCHING? —THE CONDUCTOR

  Miles showed the message to Jax.

  "He's congratulating us for stopping him?" Miles said.

  "He's thanking us for proving his point," Jax corrected. "The official ambulance never reached the hospital. Without our intervention, Sophie would have died. That proves the algorithm kills people."

  "That proves The Conductor is willing to let people die to prove the algorithm kills people."

  "That proves The Conductor is using real lives as demonstration tools."

  Miles felt sick. They'd saved Sophie, but how many other Sophies were dying because official emergency response couldn't navigate gridlock that TMA's algorithm deliberately created?

  His interface chimed again: YOUR LIVESTREAM RECORDED EVERYTHING. FIFTY-THREE THOUSAND WITNESSES SAW THE GRIDLOCK AND THE BLOCKED AMBULANCE AND YOUR ALTERNATIVE ROUTING. THEY SAW PROOF THAT THE SYSTEM IS BROKEN. THAT'S MORE VALUABLE THAN ONE LIFE. THAT'S EVIDENCE THAT CAN SAVE THOUSANDS. DO YOU UNDERSTAND NOW WHY I DO WHAT I DO? —THE CONDUCTOR

  "He's justifying using Sophie as demonstration," Miles said.

  "He's using engineering ethics—one life versus thousands—but he's forgetting that one life is still a life."

  They returned to headquarters where Captain Reyes was waiting.

  "You saved the patient," Reyes said. Not a question.

  "Yes," Jax confirmed.

  "Good. But you also proved The Conductor's point about systematic emergency response failure and now you're even more deeply involved in his operations whether you want to be or not."

  "We had to save her," Miles said.

  "I know. But now The Conductor knows you'll respond to his operations and you'll try to stop them and you'll inadvertently help him prove his points about system corruption. He's using you."

  "We're using him," Jax said. "He provides scenarios that demonstrate system failures and we document those failures and gather evidence that can be used to prosecute TMA."

  "That's very optimistic interpretation of being manipulated by wanted criminal."

  "That's very strategic interpretation of complicated alliance."

  Reyes looked at them both. "The Conductor is escalating. Today he used a real child's medical emergency. Tomorrow he might do worse. You need to decide if you're trying to stop him or trying to work with him because right now you're doing both badly."

  She left them to think about that.

  Miles checked his stream where his audience was exploding with discussion—fifty-three thousand people debating ethics and algorithms and emergency response and whether The Conductor was hero or villain.

  No consensus. Just argument.

  Like everything else in this investigation.

  Which somehow makes this worse.

  They also proved the city would’ve let her die — bad.

  Very bad.

  He didn’t lose.

  He just adjusted his hypothesis.

  congrats — that’s the point.

  respect ??