Chapter 20 Wren
Wren
The system refreshes again.
I don’t touch the keyboard.
I don’t move.
The laptop screen glows in the dark kitchen like a warning beacon.
Phase Two: ACTIVE
The words sit there in cold white letters.
My pulse pounds in my ears.
“No… no, no, no…”
I lean closer to the screen.
Scrolling through the code as fast as I can.
The activation log opens automatically.
Timestamp: 02:48 AM
Location tags begin lighting up across the map.
Montana.
Idaho.
Wyoming.
Utah.
Colorado.
Each node blinking to life like a constellation spreading across the western half of the country.
Whatever Phase Two is—
It just started everywhere.
I grab the radio.
“Boone, you need to come back to the cabin.”
“What did you find?”
“The system just activated Phase Two.”
Silence for a second.
Then Boone’s voice returns, tighter now.
“Wren… what does Phase Two mean?”
I wish I knew.
“I’m trying to figure that out.”
“Try faster.”
“Working on it.”
I set the radio down and start digging deeper into the system.
The backend architecture is enormous.
Layers of protocols buried inside civilian infrastructure databases.
Emergency services.
Transportation routes.
Medical supply chains.
Communication towers.
Every major emergency response system tied into one hidden framework.
And now—
Something inside that framework just woke up.
The map expands again.
A new panel opens on the side of the screen.
ACTIVATION PROTOCOL
My stomach tightens.
“This can’t be good.”
I open the file.
Lines of code scroll down the screen.
Most of it is routing logic.
Resource allocation.
Command hierarchy.
Exactly the kind of structure you’d expect if someone was preparing to coordinate large-scale emergency response.
Except for one section.
It’s highlighted in red.
CASCADE MONITORING
I click it.
The system loads another screen.
Graphs appear.
Data streams.
Infrastructure metrics.
Power grids.
Transportation throughput.
Internet backbone traffic.
Emergency call volume.
All monitored in real time.
My breath catches.
“Oh my god.”
Because several of the graphs are already climbing.
Not slowly.
Rapidly.
Emergency calls.
Power fluctuations.
Traffic congestion.
Supply chain delays.
All increasing simultaneously.
Across multiple states.
My hands move across the keyboard again.
Pulling up national infrastructure reports.
Looking for confirmation.
The first alert appears seconds later.
Regional power disturbance.
Idaho.
Then another.
Freight rail delays.
Wyoming.
Then another.
Cell tower overload warnings.
Colorado.
My chest tightens.
“These aren’t isolated.”
They’re connected.
Exactly like the Architect predicted.
I scroll further down the activation panel.
And find something much worse.
A timer.
Large.
Centered.
Counting down.
12:00:00
Twelve hours.
My heart pounds harder.
“What happens in twelve hours?”
The system answers before I can even finish the thought.
A document opens automatically.
Authorization required.
But the system doesn’t ask for credentials.
It already granted them.
The title appears across the screen.
PHASE THREE — LEADERSHIP TRANSFER
I stare at it.
“Leadership transfer?”
The radio crackles again.
Boone’s voice.
“Wren, we’re on the way.”
“Good.”
“What did you find?”
I hesitate.
Because I’m not sure how to say it.
“The Architect wasn’t just predicting collapse.”
“What do you mean?”
I look back at the infrastructure graphs.
At the rising emergency indicators.
At the countdown ticking quietly on the screen.
“He built a system to take control when it happens. I think he controls everything.”
Boone is quiet for a moment.
Then he asks the question we’re all thinking.
“Is the collapse starting?”
I swallow.
“I don’t know yet.”
“But the system thinks it is.”
Outside the cabin, the wind rises again.
Pushing through the trees like a storm building in the mountains.
And somewhere inside a hidden network spread across half the country—
A machine built years ago by Sentinel…
Now guided by the Architect…
Has begun preparing to take control.
And according to the countdown on my screen—
In twelve hours…
It will try.