Chapter 18 Wren

Wren

The cabin is quiet again.

Too quiet.

The trucks are gone.

Adam. Russ. Boone. Blade. Miles.

All of them in town dealing with the aftermath of whatever just happened at the church.

Which leaves me alone with the system.

And the more I look at it—

The more wrong it feels.

The recruitment database still glows on the laptop screen.

Names.

Profiles.

Skill assessments.

Leadership probability.

It reads less like a volunteer list and more like a military command selection board.

I scroll through the backend code again.

Someone built this system carefully.

Layer by layer.

Hidden inside what looks like a civilian emergency-response network.

Brilliant.

Terrifying.

And incredibly familiar.

I pause.

Because that feeling again.

The one that keeps nagging at the back of my mind.

I’ve seen something like this before.

I open a new window and start searching older intelligence archives.

Sentinel operations.

Infrastructure mapping.

Leadership modeling.

The files load slowly.

Most of Sentinel’s work was wiped from official databases after his network collapsed.

But not everything disappears.

Some fragments always survive.

The first document appears.

An old analysis report.

Title: Distributed Civilian Response Framework

My pulse quickens.

“That sounds familiar.”

I open it.

The document outlines a theory.

Disaster-response networks embedded inside civilian systems.

Volunteer groups.

Church organizations.

Medical supply chains.

Search-and-rescue units.

Each one functioning independently.

But connected through a hidden command structure.

Exactly like the system on my screen.

My stomach tightens.

“No way.”

I scroll further down.

A footnote catches my eye.

Program architect: Sentinel Initiative — Phase One

The air leaves my lungs.

“This wasn’t his idea…”

I open the network code again.

Comparing structures.

Encryption patterns.

The architecture is identical.

Meaning the truth is suddenly very clear.

Sentinel didn’t just inspire this network.

He started it.

My heart pounds harder as I dig deeper.

More files appear.

Old satellite infrastructure proposals.

Civilian communication relays.

Volunteer response grids.

Every single concept matches the system currently spreading across the western United States.

But the documents stop abruptly.

The final entry reads:

Phase One complete.

Then nothing.

No Phase Two.

No Phase Three.

Just silence.

I lean back slowly in the chair.

Which means someone else finished it.

The Architect.

My eyes move back to the recruitment database.

Boone’s name.

Adam’s name.

Leadership candidates.

Command selection.

My stomach twists.

Because now the pattern is becoming clear.

Sentinel built the framework.

The Architect is building the leadership.

I grab the radio.

“Adam, come in.”

Static crackles.

Then his voice answers.

“Go ahead.”

“I found something.”

“What kind of something?”

“The network.”

A pause.

“Yeah?”

“It didn’t start recently.”

“How old is it?”

I swallow.

“Years.”

“How many?”

I look back at the Sentinel file.

Then answer quietly.

“Over a decade.”

Silence fills the radio.

Then Boone’s voice cuts in.

“You’re saying someone’s been building this thing for ten years?”

“Yes.”

Adam’s voice lowers slightly.

“Who started it?”

I hesitate.

Then say the name.

“Sentinel.”

The radio goes completely silent.

For several seconds no one speaks.

Then Boone’s voice finally comes through.

Low.

Controlled.

“Explain.”

I stare at the files again.

At the architecture hidden inside the code.

“At some point Sentinel designed a distributed civilian response network.”

“For disasters?”

“Originally.”

“And now?”

“Now someone else is finishing it.”

Adam exhales slowly over the radio.

“The Architect.”

“Yes.”

Russ mutters something under his breath.

“Great.”

Boone’s voice returns.

“What’s the endgame?”

I look at the leadership probability field again.

The command candidate tag.

The map full of nodes stretching across half the country.

And suddenly the answer feels obvious.

“They’re preparing for systemic collapse.”

“What kind of collapse?” Adam asks.

I shake my head slowly.

“I don’t know.”

“But whatever it is…”

My eyes move to Boone’s file again.

“…they believe it’s coming soon.”

The wind rattles the cabin windows again.

Cold.

Restless.

And somewhere out there—

The Architect is still watching the board.

Still selecting players.

Still deciding who leads the army when the world finally breaks.

And tonight—

Boone and Adam just moved to the top of the list.

If ads affect your reading experience, click here to remove ads on this page.