Chapter Twenty Five: Cascade

The room they were brought to on Wednesday morning had no name on the door.

It did not appear in the building directory or on the campus map Julian had memorized during his first week. The corridor branched from the academic wing at an angle that made him revise his understanding of the rooms around it. As though someone had tucked a space into the architecture the way you tucked something into a pocket you did not want found.

Cohort Two arrived in ones and twos, following the notification that had appeared at seven.

SCENARIO BRIEFING: COHORT TWO
LOCATION: OPERATIONS LAB 4
ATTENDANCE REQUIRED BY 07:30
NO ADVANCE BRIEFING AVAILABLE

Inside, the room looked nothing like Monday’s assessment spaces.

Those had isolated a person and a task. This one seemed to expect events to happen faster than anyone could comfortably follow.

Curved displays formed a semicircle around an open floor. Physical keyboards sat beside haptic surfaces. Chairs faced slightly away from one another, toward work already waiting on their screens.

Halvorsen stood in the center.

Morse sat at the back.

Beside Halvorsen was a man Julian did not recognize. Mid-forties, close-cropped hair, hands resting loosely at his sides. No name tag. No lanyard. He looked as though waiting had long ago ceased to require a particular posture.

The students found their stations.

Zara took the far left, laying her hands open on the console. Kael sat beside her, looking around with his usual unhurried attention.

Leena arrived last. She stopped inside the door for three seconds before entering.

Julian watched her gaze move over the displays, the floor, the heavy equipment along the eastern wall. Reading something in the arrangement he could not.

“Good morning,” Halvorsen said.

She waited until the last chair stopped moving.

“You are not going to like the next few hours.”

The displays activated together.

The continental United States appeared beneath a web of light.

Power transmission in amber. Gas pipelines in blue. Water networks in green. Telecommunications in white. Financial settlement systems in cold silver.

A country rendered as a nervous system.

Julian could see where one network passed beneath another, where several depended on a single point. The map made visible how much of ordinary life rested on things most people never had reason to think about.

Then the red began.

A node in the Pacific Northwest.

Three transmission substations.

Seventeen seconds later, a water-treatment network along the Gulf Coast.

Then more, spread across time zones, each beginning before the previous breach finished unfolding.

“This is a simulation,” Halvorsen said. “The infrastructure architecture, vulnerability chains, and attack methods are drawn from documented systems. The scenario was developed in consultation with the Department of Homeland Security.”

The unfamiliar man spoke.

“You’re looking at a coordinated infrastructure attack. It began at six Eastern, thirty-one minutes ago in scenario time. Seven primary breach vectors have been identified. Assume there are things you haven’t found.”

His voice was level. He did not seem concerned about whether they found that reassuring.

“Stopping the intrusion is only part of the task. You must stabilize the systems, manage the consequences for affected populations, and maintain stakeholder coherence.”

“Stakeholder coherence,” Aisha repeated.

“Governors. Emergency management. Congressional oversight. The press. The public.”

He looked toward her.

“A technical fix is of limited use if the officials responsible for acting on it have already committed to incompatible decisions.”

Mateo leaned toward the map.

“Your stations reflect your assessment profiles,” Halvorsen said. “You have ninety seconds to orient. Then the clock resumes.”

SCENARIO: CASCADE
INITIAL BREACH: T+00:00
CURRENT TIME: T+00:31
ACTIVE ATTACK VECTORS: SEVEN CONFIRMED
POPULATION AT RISK: 34 MILLION DIRECT / 180 MILLION THROUGH CASCADE EFFECTS

Julian opened his assignment.

JULIAN REYES: RAPID RESPONSE COORDINATOR

THREAT TRIAGE / CROSS-TEAM ROUTING / FIELD DECISION AUTHORITY

Resolve conflicts between domains. Allocate personnel and time.
Override authority enabled.

He read the last line again.

Then he looked at the seven red points.

Their distribution was too deliberate. Someone had chosen them for what happened between them, not simply for the damage each could do alone.

He began tracing the relationships.

“Ninety seconds,” Halvorsen said.

The clock moved.

T+00:32 — Power Grid

The Pacific Northwest drew the eye the way a fire did.

Three high-voltage substations were offline. Their loss had severed major transmission paths from the Columbia River hydroelectric complex. Automatic systems were already redistributing the load.

The alternate paths had been compromised too.

They were waiting for the redistribution.

Theo configured his station in less than forty seconds. He bypassed the haptic workspace and opened the underlying control architecture.

“They’re still in the controllers,” he said. “Persistent process. It looks like routine diagnostics.”

“How long to find it?” Julian asked.

“Found it.”

Theo enlarged a section of the system.

“I’m checking what happens if I remove it.”

Julian looked at him.

“It has a final action?”

“Several.”

Theo followed a dependency into another layer.

“Remove it the wrong way and it issues a last set of commands.”

“What commands?”

A short pause.

“It pushes the affected network toward simultaneous transformer overload.”

Julian looked back at the amber lines.

A breaker could trip and reset. A burned transformer could leave a place dark long after the people who broke it had moved on.

“Recovery estimates run from weeks to eighteen months, depending on damage,” Mateo said. “Hospitals on generators. Water treatment losing power—”

“Don’t finish that,” Ethan said.

“It’s outside the scenario’s recovery window.”

“I know,” Julian said. “Theo. What do you need?”

“Time. And less talking.”

Julian turned back to the map.

The Gulf Coast breach continued spreading. Three facilities had gone to manual operation. Their systems still worked, but the safety margins now depended on people making decisions under pressure.

He opened the team channel.

[REYES → ALL] Gulf water nodes on manual. Watch the interaction between operator decisions. Someone take that.

[Leena → REYES] I have it.

Theo’s hands stopped.

“It’s out.”

PRIMARY GRID INTRUSION: REMOVED
TRANSFORMER STATUS: NOMINAL

SECONDARY PROCESS DETECTED IN BACKUP CONTROLLERS.
STATUS: DORMANT.

“There’s another one,” Theo said.

“I see it.”

“It’s waiting for something.”

“For us to think we’re finished,” Mateo said.

Julian studied the dormant marker. It sat beneath the cleared breach, small enough to overlook if you wanted to believe the green indicator above it.

“Watch it,” he said. “Work out the trigger before touching it.”

Theo nodded and established a monitoring thread.

Julian was already looking toward the Gulf.

T+00:44 — Water Treatment

Leena found that the water-treatment problem was becoming harder as the operators worked to make it safer.

The original intrusion was relatively simple. It had disrupted automation and left trained people managing the process manually.

Individually, their decisions made sense.

Together, they were moving toward a contamination event.

Three supervisors were adjusting their facilities in response to one another. Each correction changed the conditions the others were trying to correct. The plants remained functional. The communication between them was careful and professional.

The feedback loop was not.

Leena watched the pressure histories beside dosing records and the shared operations log. The relationship appeared gradually, then all at once: three defensible approaches combining into something none of the supervisors could see from a single station.

It reminded her of the sealed box.

The answer was distributed across things that did not seem sufficient on their own.

“I need a joint channel,” she said.

Julian glanced over.

“With the operators?”

“All three supervisors.”

He was tracking four other flags. She could see him move one aside to make room for hers.

“You have it.”

Leena opened the line and listened.

Facility Two’s supervisor spoke with the greatest confidence. The others deferred to him without explicitly agreeing that he was in charge.

His last two adjustments had been slightly wrong.

Their corrections had carried the error outward.

She did not begin by telling him that.

Instead, she asked Facility Three’s supervisor to compare the chlorine residual with the changing distribution pressure.

A technical question. Something he could answer from his own readings.

He worked through it aloud.

“Which would mean, at the current upstream pressure, we should be seeing a higher margin than…”

He stopped.

Leena watched four seconds pass.

Then Facility Two came back.

“I see it. Hold the next adjustment. I need to recalibrate the last two cycles.”

The loop broke quietly.

A change entered the record. The others responded to the corrected values. Facility Three began asking for confirmations, and the conversation reorganized around him without anyone announcing a new lead.

Leena watched the traces settle.

GULF WATER NETWORK: MANUAL OPERATION STABLE
CONTAMINATION RISK: LOW
CONTROL-SYSTEM INTRUSION: STILL PRESENT

“I need the intrusion removed,” she told Julian.

“Theo’s tracing the grid secondary. Can you handle this one?”

She opened the architecture.

It was simpler than what she had seen on Theo’s screen. Less protected. Built to create confusion quickly, not to survive a sustained examination.

“Eight minutes.”

“The financial network is moving. Can you do five?”

Leena brought the plant logs alongside the control sequence.

“I’ll tell you if I can’t.”

She finished in four.

T+01:02 — Financial Infrastructure

BENJAMIN LEVY: EXCEPTION PATH ANALYST

FAILURE-MODE IDENTIFICATION / ERROR RECOVERY / FINANCIAL NETWORK SUPPORT

Prioritize what the system does after it fails.

Ben stared at the assignment.

“Great. They made my entire personality a job description.”

The attack on financial settlement was not shutting anything down.

That made it harder to see.

Transactions remained in motion. Interbank payments, payroll, government disbursements. Each appeared to be progressing until another small uncertainty returned it to a retry process.

Forty-eight to seventy-two hours of delay.

No reliable explanation for anyone waiting on the money.

Across the rest of the scenario, uncertainty was already becoming inaction. Hospitals could not confirm payroll. Suppliers suspended credit. Emergency managers hesitated over resources they could not be certain they could pay for.

The response to every other breach was beginning to slow.

“The technical fix isn’t the whole problem,” Aisha said.

Julian turned.

“Ben can work the exploit. Maybe twenty minutes.”

Ben looked up.

“I appreciate the confidence. I should clarify that twenty minutes is the optimistic estimate of someone who hasn’t watched me interact with a hostile banking interface.”

“Can you do it?”

He looked back at the process.

A failed settlement generated a retry. Each retry inherited enough doubt from the previous one to remain unresolved.

A door reopening because the latch kept reporting that it had never properly closed.

“Probably. Strongly adjacent to yes.”

“Ben,” Julian said.

“Yes.”

Aisha enlarged three communications feeds.

“Three governors have issued statements. One has the cause wrong. One has the timeline wrong. The third is accurate, but he’s framed it as though the other two are incompetent.”

“That’s political,” Mateo said.

“It’s already affecting the response. Their agencies are following incompatible instructions.”

At the back of the room, the stranger spoke.

“Correct.”

Several heads turned.

Ben kept working.

He stopped trying to clear individual payments and began following what each failure told the next attempt to believe.

“It’s not just delaying money,” he said. “It’s delaying certainty.”

Aisha turned toward him.

“That matters.”

“I hoped so. Otherwise I was being dramatic while losing to accounting.”

“What do you need?” Julian asked her.

“The governor who has the cause wrong, before his next statement. And a shared technical summary. Enough detail to align the agencies without turning this into three officials arguing over who misunderstood first.”

Ben lifted a finger.

“That sounds…”

“Like giving them a way to correct course.”

“Three emotionally compatible doors.”

“Yes.”

“Okay. I hate that I understand that.”

Aisha opened the governor’s channel.

Julian watched her listen.

She did not hurry the man past his explanation. She asked which agencies had already acted, which decisions remained reversible, what he needed confirmed before changing the guidance.

Each answer gave her the next question.

Four minutes passed.

Julian watched the clock and left her alone.

[GOVERNOR HAYES — PRESS ADVISORY]

Updated technical assessment indicates a disruption to transaction verification. Remediation is underway, with restoration currently expected within two hours. State agencies should follow the revised coordination guidance.

STAKEHOLDER STATUS: SHARED RESPONSE GUIDANCE ADOPTED

Aisha closed the channel.

Then she opened the next flag.

T+01:19 — Convergence

Mateo had been following a projection he did not want to announce before he was certain enough.

Now he was.

“Julian. The seven breach points aren’t the whole attack.”

Julian looked over.

“They’re preparation.”

Mateo moved his model to the shared display.

The seven red points faded beneath their downstream effects.

Load redistribution. Delayed maintenance. Degraded communications. Emergency purchases and generation changes crossing regional boundaries through systems that did not share a single operator.

The effects overlapped across the mid-Atlantic.

“They’re setting up a blackout here.”

He marked the region.

“Thirty-two to forty minutes. Fourteen million people.”

A weather layer appeared.

The scenario was set in January.

Julian saw the temperatures and began thinking about heating systems, hospitals, people alone in apartments above the reach of working elevators.

He stopped.

“How confident?”

“Ninety-one percent. The other nine depends on one of their intermediate steps failing. I wouldn’t plan around that.”

Julian looked at the board.

Four initial vectors addressed. Three active. The dormant grid process still waiting in the Northwest.

“Theo. Secondary grid process becomes priority one.”

Theo brought it forward.

“I think it’s waiting for the convergence,” Julian said. “Not for us to remove it. For the other grid to come under stress.”

Theo followed the trigger input.

“Yes.”

He leaned closer.

“It’s reading a load threshold in the Eastern Interconnection. When that threshold is crossed, it hits the Northwest again.”

Two crises timed to become one national demand for help.

“Can you neutralize it first?”

“Yes. Probably. It’s cleaner than the original.”

Theo’s fingers moved.

“If I disturb the wrong part, it runs early.”

“How long?”

“Twelve minutes.”

“I need eleven.”

Theo did not answer. He was already working.

Julian turned.

“Zara.”

T+01:22 — Extension

Zara’s assignment had required little explanation.

INFRASTRUCTURE RELAY COORDINATION
CATALYST-MEDIATED FIELD INTERFACE

Three constructs stood against the rear wall.

She had felt them when she entered. For the last forty minutes, she had maintained a light connection beneath the rest of her attention.

“The model identifies three relay stations,” Julian said. “They need physical reconfiguration. Two have lost remote access through the telecom breach.”

Zara looked at the stations.

“All three at once?”

“Yes. The constructs will operate the simulated field interfaces. One station needs a live switchover.”

She deepened the connections.

Two days ago, she had discovered how to reach them. Now the adjustment felt deliberate, stable, almost familiar.

CONCURRENT CONNECTIONS: THREE
FIELD REPRESENTATIONS: ALPHA-7 / ALPHA-9 / BRAVO-3

“Bravo’s sequence,” she said.

“Sending,” Mateo answered.

The instructions arrived in two stages, twelve linked steps. Timing windows narrowed in the middle.

She read them once.

Around the room, the constructs moved into their assigned interfaces. Through them, the simulation gave her three locations.

Alpha-7 was clear.

Alpha-9 had an obstructed access panel.

Bravo-3 carried a faint vibration through its controls.

She held the three places together.

At Alpha-9, the primary route would not open. She redirected the unit through the secondary access without stopping the others.

Bravo required more.

She reached the first narrow timing window. Four seconds to establish the condition. Seven to complete the next transition.

The unit’s sensors gave her the alignment as a subtle change in vibration. She recognized it without having to translate it into a number first.

The interlocked sequence continued.

Release. Redirect. Reinitialize.

A hesitation between those actions would have made them separate problems. She carried them as one movement.

At the final step, the load-balancing tolerances existed in her attention as values and as something like balance itself: the feel of weight settling where it could be held.

ALPHA-7: CONFIGURATION COMPLETE
ALPHA-9: CONFIGURATION COMPLETE
BRAVO-3: SWITCHOVER COMPLETE

MID-ATLANTIC CONVERGENCE PATH: INTERRUPTED
PROJECTED BLACKOUT: PREVENTED

COMPLETION: 9 MINUTES, 14 SECONDS
CONVENTIONAL FIELD-TEAM ESTIMATE: 47–82 MINUTES

Zara eased the active connections back.

She did it as though setting something down carefully.

The carrier remained.

T+01:29 — Secondary

While Zara worked, Theo found his way into the dormant grid process.

He had eleven minutes.

He used nine.

The secondary intrusion was tighter than the original. Fewer dependencies. Less unnecessary structure. The first had offered him places to work because of its complexity.

This one gave him very little.

But its trigger depended on information arriving from somewhere else.

Theo followed that dependency.

He did not need to tear the process out while it was capable of reacting. He needed to make certain the event it awaited could never arrive.

He changed the condition it was monitoring.

The process remained intact, patient and inactive, waiting for a threshold beyond the scenario’s operating range.

Theo considered removing it entirely.

Then he looked at the communications path leading back from it.

“Secondary is neutralized,” he said. “I’ve blocked the automatic trigger. The process is still there.”

“Why leave it?” Julian asked.

“If I remove it, they may notice and replace it. Leave the shell and they may think it’s still waiting.”

Theo opened another monitor.

“If they try to activate it directly, we can see where the attempt comes from. I’m containing that path separately.”

Julian was quiet for a moment.

“Keep the watch independent of the process.”

“Already doing it.”

SECONDARY GRID PROCESS: CONTAINED
AUTOMATIC TRIGGER: DISABLED
COMMUNICATION MONITORING: ACTIVE

Theo looked at the small, unchanged shape of the intrusion.

A thing could appear to be exactly what its maker intended and no longer obey them.

He knew how useful that was.

T+01:33 — Signal

Tamar had been working the telecommunications breach longer than anyone had been working a single problem.

It was the least dramatic system on the board.

She distrusted it for that reason.

“It’s reducing redundancy,” she had told Julian earlier. “Leaving the main paths intact and quietly making the alternatives worse.”

“So recovery loses its backup.”

“And every system we fix has a harder time staying fixed.”

The intrusion was altering route preferences across the backbone. Critical messages still arrived, but increasingly by paths with more delay and higher error rates.

It had spread through forty-seven routing tables across fourteen major nodes.

Each correction was manageable.

There were too many.

“I need another person,” Tamar said. “Someone to hold a second thread.”

Julian checked the board.

Theo was establishing the grid watch. Leena had finished the water network and was helping Ben clear financial residue. Mateo’s projection kept changing. Zara’s field work was still completing.

“Kael.”

He looked up from general monitoring.

“The routing work is precise,” Julian said. “Systematic. Tamar can brief you.”

Kael stood and moved to the adjacent station.

He listened for thirty seconds.

Then he read the first table. The second.

His posture straightened slightly.

The next three tables passed beneath a different quality of attention.

“I see the pattern,” he said.

The cadence was more clipped.

“They’re adding twelve to eighteen milliseconds to selected traffic classes. The classification is consistent. We can filter for it.”

Tamar stared at her screen.

She had been checking row by row.

“Show me.”

He did.

Their corrections began advancing across the map.

TELECOM ROUTING TABLES RESTORED: 31 OF 47

At the thirty-second table, something responded.

Not an alarm.

A question.

The intrusion had noticed its work being reversed and begun deciding whether it was seeing automatic recovery or deliberate intervention.

“It’s checking us,” Kael said.

“How long?”

“Forty seconds. If it identifies active intervention, it accelerates the remaining changes.”

“Can we finish?”

He looked at the queue.

“Not at this rate.”

“Julian.”

“Heard. Theo, telecom. Now.”

Theo shifted to the new thread.

Sixteen tables remained.

Thirty-one seconds.

Tamar worked faster than she could comfortably verify. Each value needed to be right the first time. Her eyes kept reaching toward the next field before her fingers finished the current one.

Theo took a broader approach.

“I’m reverting against the clean baseline,” he said. “Some legitimate preferences will go too.”

“How much impact?” Julian asked.

“Suboptimal routes. Working connections.”

“Do it.”

The remaining markers changed.

Forty-two.

Forty-five.

Forty-seven.

TELECOM ROUTING TABLES RESTORED: 47 OF 47
HOSTILE ASSESSMENT PROCESS: ABORTED
COMMUNICATION REDUNDANCY: RESTORED

Tamar let her hands stop.

Beside her, Kael sat back. The change in him was quieter on the return.

“That was good work,” she said.

He looked toward her.

“Thank you. They did well.”

T+01:48 — Kinetic

The seventh vector had waited at the bottom of the board because no amount of clean code could finish it.

The primary controls at the scenario’s Hoover Basin Reservoir had been taken offline. A follow-on physical attack had destroyed the backup automation.

Three emergency spillway gates remained available through manual operation.

The reservoir was at ninety-four percent capacity.

The water behind the dam did not care about the reason.

“Inflow is above the model’s earlier estimate,” Mateo said. “Forty-one minutes before overtopping becomes likely. Seventy-three before the projections reach critical.”

“Engineering crew?” Julian asked.

“Ninety minutes at minimum. Single mountain access road.”

Julian turned toward the eastern wall.

The rig had been there since they arrived.

Three actuator assemblies bolted to a steel frame spanning fourteen meters. Hydraulic resistance systems. Heavy wheels and levers. A physical representation of gates weighing forty thousand pounds, loaded against a nearly full reservoir.

“Ethan.”

He was already getting up.

“The first two gates have to begin opening within ninety seconds of each other,” Mateo said. “The third within sixty seconds of the second. Fixed order, left to right. Once you engage a gate, complete the sequence before moving.”

Ethan looked along the frame.

“What force?”

“The initial resistance is calibrated to roughly a three-hundred-and-forty-kilogram load at the operating point. Lower once it breaks free. Standard procedure uses two people and mechanical assistance at each gate.”

Ethan crossed to the first wheel.

He laid both hands on it without turning.

Felt where it sat.

“About twenty seconds each,” he said. “If nothing goes wrong.”

“That fits the window,” Julian said.

“I said if nothing goes wrong.”

Julian looked at the reservoir projection.

“Go.”

Ethan loaded his weight into the first wheel.

Nothing moved.

He reset his grip and increased the force. The resistance traveled through his arms into his shoulders, absolute until something deep in the mechanism shifted.

The sound reached his chest before his ears.

The wheel began turning.

GATE ONE: 40% OPEN

Eighteen seconds.

He stayed through the remaining travel, completed the lever throw, then moved to the second assembly.

The second was worse.

He felt it immediately and changed his stance.

“Ethan,” Mateo said.

“I know.”

The mechanism had passed the point where the first had yielded.

The clock reached forty-four seconds.

“It’s seized,” Zara said.

“Not yet.”

His voice was tight but steady.

“Resistant.”

He gave it more.

A bass note traveled through the floor and up Julian’s legs. Water rippled in Zara’s glass. The nearest display trembled on its mount.

The wheel jerked beneath Ethan’s hands.

He caught the movement and carried it through.

By fifty-eight seconds, the second gate was traveling cleanly.

He finished the sequence and crossed to the third.

This one yielded earlier.

He did not waste the difference.

MANUAL OPERATION: 01:22

GATE ONE: FULL OPEN
GATE TWO: FULL OPEN
GATE THREE: FULL OPEN

RESERVOIR LEVEL: STABILIZING
OVERTOPPING PROJECTION: CLEARED

Ethan stepped back.

For a moment, the only sound near the rig was his breathing.

“That was…” Ben began.

He did not find the rest.

“The third was easier,” Ethan said.

He kept looking at the wheel.

“If it had been like the second, it would’ve been close.”

The scenario report appeared.

THREE MANUAL GATE SEQUENCES COMPLETED: 82 SECONDS

STANDARD CREW OPERATION: MINIMUM 18 MINUTES
SINGLE-OPERATOR, UNASSISTED BENCHMARK: NOT ESTABLISHED

CALIBRATED RESISTANCE EXCEEDS STANDARD UNAIDED HUMAN OPERATING RANGE.

Julian read the final line.

Ethan was rubbing one palm with the thumb of his other hand.

T+02:01 — Consequences

The notification struck Julian’s console like a stone through glass.

EIGHTH ATTACK VECTOR DETECTED

EMERGENCY DISPATCH: NORTHEAST CORRIDOR

CALLS ROUTED TO INCORRECT JURISDICTIONS OR FAILING TO CONNECT

AFFECTED POPULATION: 8.3 MILLION

ESTIMATED CALL ATTEMPTS DURING DISRUPTION: 700–900

Julian read it twice.

“Everyone stop.”

The room quieted.

“Emergency dispatch. Northeast. Wrong jurisdictions, failed connections.”

He opened the timing estimate.

“It’s been running for nineteen minutes.”

No one spoke.

“Mateo. Confirm.”

“Checking.”

Julian watched the older alerts in the dispatch log resolve into a pattern.

“Yes,” Mateo said. “Nineteen minutes. It was masked by the telecom degradation. We didn’t identify it as a separate vector.”

“While we were fixing that system.”

“Yes.”

Seven original vectors addressed.

The blackout prevented. Water stable. Payments recovering. Gates open.

And underneath all of it, people had been calling for help.

The scenario had estimated between seven hundred and nine hundred attempts. Julian could not tell how many represented repeat calls. How many had eventually connected.

How many had stopped.

“Theo. Dispatch.”

“Already opening it.”

A few seconds.

“Routing corruption. Simpler than the backbone attack. Built to be missed, not to survive once we found it.”

“How long?”

“Six minutes.”

“Four.”

“Five.”

Julian nodded.

“Aisha.”

She was already looking at him.

“The people who didn’t get through. Some will try again. Some—”

“I know.”

“What can we do?”

She opened the emergency broadcast interface.

“We can reach the region faster than we can identify every failed caller. Tell people emergency response is still active. Ask anyone whose call didn’t connect to try again.”

“Can the lines take that before Theo’s finished?” Ben asked.

“Some are working. Some are misrouting. We’re getting nothing to the people who have given up.”

Aisha looked at Julian.

“We can send a short message now and explain the disruption when the repair is confirmed.”

“That leaves out why they couldn’t connect,” Ben said.

“Yes.”

Her hands stayed above the controls.

“It gets them moving before the full statement is ready. But it may also send some people back into a line that still fails.”

Julian looked at the nineteen-minute window.

He thought of his mother, of a phone held too tightly, of how long it could take a ringing line to become something you no longer trusted.

He did not have a version of the decision without a cost.

“Send it. Say responders are operating. Don’t say every line is clear. When routing is restored, follow with the full disruption notice.”

Aisha nodded.

REGIONAL EMERGENCY ADVISORY

Emergency responders remain active throughout the affected region. If an emergency call has failed to connect, please try again. Further service information will follow shortly.

The message left the console.

Julian watched the dispatch map while Theo worked.

Four minutes and forty seconds.

Then the routing indicators began turning green.

EMERGENCY DISPATCH: RESTORED
JURISDICTION ROUTING: VERIFIED

Aisha released the follow-up.

Julian felt nothing that resembled relief.

T+02:09 — Signature

Leena had been quiet long enough that Mateo looked toward her.

Julian noticed him looking and followed his gaze.

She was no longer working at her console.

She was studying the main map.

All the vectors remained visible there, along with the recovered systems, the timing histories, the lines showing what had depended on what.

“Leena.”

She lifted one hand.

Wait.

He waited.

For another forty seconds, she did not speak.

Then: “The attack has a signature.”

Mateo turned toward her.

“What kind?”

“The tools differ. The decisions don’t.”

She enlarged the sequence.

“The interval between deployments. How much disruption each vector creates before the next begins. The way the dispatch attack sits beneath the telecom problem.”

Her finger moved between two timestamps.

“These weren’t independent choices.”

“They planned for us,” Theo said.

“For a response,” Leena said. “I don’t know whether they planned for us.”

At the back of the room, the unfamiliar man had become still.

“The dispatch vector uses a gap a competent response team would leave,” Leena continued. “They knew we’d focus on restoring backbone function. They used that work to keep the smaller failure from standing out.”

“They understood the protocol,” Aisha said.

“More than the protocol. The attention.”

Julian looked toward the back.

The man was looking at Leena.

“Can you characterize who built it?” Theo asked.

She kept studying the map.

“Patient,” she said. “Technically sophisticated, but they didn’t always choose the most complicated method. They chose things that would work reliably.”

She brought up two unused branches.

“These look prepared but undeployed. Contingencies. Something was watching our response and deciding which to use.”

The map held its green and amber light.

“They could have caused more damage,” Leena said. “At least in the model we can see. They held some options back.”

“Why?” Julian asked.

“I don’t know.”

The stranger stood.

“What you’re describing has a name,” he said.

Leena looked at him.

He paused.

“Keep thinking about it.”

“I’m describing what’s there.”

“Yes,” he said.

Then he looked toward Halvorsen.

“Scenario complete.”

CASCADE: CONCLUDED
SCENARIO CLOCK: T+02:11

ATTACK VECTORS ADDRESSED: EIGHT OF EIGHT
CATASTROPHIC OUTCOMES PREVENTED: CRITERIA MET
STAKEHOLDER COORDINATION: MAINTAINED

POTENTIAL HARM DURING DISPATCH DISRUPTION: UNRESOLVED

UNSCHEDULED FINDING: ATTACKER-SIGNATURE ANALYSIS

Halvorsen gave them ten minutes.

No one left.

Ethan sat on the floor against his station, forearms resting on his knees. Zara folded her hands in her lap. Kael stood at the narrow window near the rear of the lab, looking out at the grounds.

Julian stayed in the coordinator chair.

The map remained on the wall.

He could still find the dispatch breach immediately. Now that he knew where to look, it seemed impossible that he had missed it.

When the ten minutes ended, the stranger moved to the front.

“I’ll conduct the debrief. Dr. Halvorsen will follow.”

He looked at them with an attention that did not soften when they met it.

“My name is Farrell. I work with an organization advising the Institute on this phase of the program. I’ve been reviewing your progress since Phase One concluded.”

He set his display on the desk.

“We’ll begin with dispatch.”

Julian sat a little straighter.

“Nineteen minutes.”

“Yes.”

“It was designed to sit inside another failure.”

“Correct. Your analyst identified that.”

Farrell glanced toward Leena.

“What changes because you know it?”

“Verification after intervention,” Mateo said. “A wider sweep before we declare the domain stable.”

“That takes time,” Julian said.

“Yes.”

“Every time.”

Mateo looked at him.

“Some of that time will cost us somewhere else. Some will catch the next hidden vector.”

Julian looked down at his hands.

He had wanted an answer he could turn into a rule without inheriting another problem.

There did not seem to be one.

“The callers,” Ben said. “If this were real. What happens to them?”

Farrell took a moment before answering.

“Some calls would eventually route correctly. Some people would try again. Some would find another way to get help.”

Ben waited.

“Some would not.”

Ethan’s hands went still on his knees.

“That is part of the outcome,” Farrell said. “It remains part of the outcome even when every indicator is green.”

Julian looked back at the map.

“The advisory,” Farrell continued. “Why send it before restoration?”

Aisha turned toward Julian, then let him answer.

“To reach people who might have stopped trying.”

“And the risk?”

“Sending them back into a system that could fail them again.”

Farrell nodded.

“You made the tradeoff. Keep both sides in the record.”

He moved to Leena.

“Walk me through the signature.”

She did.

Without the running clock, she explained the connections more slowly. Timing. Dependencies. Reliable techniques used in combination. Prepared options that had remained unused.

Farrell did not interrupt.

When she finished, he studied the map for several seconds.

“Keep working on that,” he said.

Halvorsen stepped forward.

“The scenario was designed so that preventing every adverse consequence within the available time would be beyond the projected capability of this team.”

Julian heard Ben’s chair shift.

“We needed to observe what happened when the demands exceeded your capacity. Where you spent time. What you deferred. Whether you continued functioning after discovering the cost of a decision.”

She looked toward Julian.

“You continued.”

He could not tell whether he wanted that to be praise.

He thought about the advisory. The seconds in which Aisha had waited for him. How quickly his answer had come once he accepted that no answer would be clean.

He did not know whether the person he had been before Neurovia could have made that decision as quickly.

He was less certain than he had expected that speed was the part he wanted to understand.

***

Halvorsen closed the door after the students left.

For a moment, she stood with her back to it.

“Well,” she said.

Farrell was gathering his display.

“Send the full output logs. I’ll have recommendations by the end of the week.”

“That’s all?”

He looked at her.

“No.”

The room’s screens continued their quiet cycling.

“The rest needs a different conversation.”

***

They walked back along the corridor that had not appeared on Julian’s map.

At the junction with the academic wing, Ethan stopped.

The others took another step or two before turning.

“That was a simulation,” he said.

Mateo looked at him.

“The infrastructure was based on real…”

“I know.”

Ethan rubbed the heel of one hand.

“I mean those people weren’t actually calling. Nobody was sitting somewhere waiting because we missed it.”

“No,” Julian said. “They weren’t.”

Ethan nodded, but did not begin walking.

“Someone is making sure we could do it.”

The corridor felt colder away from the lab.

“Farrell. Whoever he works for. The DHS models.” Ethan looked down at his hands. “That rig was built to a specific force requirement.”

No one answered.

“They’re not training us for a test.”

They stood with that.

Students passed at the far end of the main corridor. Someone laughed. A door opened onto the smell of coffee and closed again.

Zara spoke.

“I could feel the constructs the whole time. Even when I wasn’t directing them.”

She looked toward the corridor they had come from.

“It felt like having more hands.”

A pause.

“It didn’t feel wrong.”

“That’s what I keep thinking about,” Leena said. “How natural it was.”

Julian remembered the coordinator station.

The way one decision had carried him into the next. Water to power to money to dispatch. Separate domains on the screens, joined inside the work until moving between them felt less like switching tasks than following something already continuous.

He remembered his mother’s question on the morning of his acceptance.

¿Te duele?

Does it hurt?

He had said no.

He had meant it.

Standing here, he could still feel the nineteen minutes. The callers represented by a range of numbers. The decision to speak before the system was fully repaired.

Underneath those things was something he had not expected to find.

Readiness.

He wanted time to understand it before anyone asked him to use it again.

He looked back down the narrow corridor.

He did not think that was the order in which it would happen.