Cops Forced a Man’s Red Sports Car Off the Road — Then Five Black SUVs Surrounded the Intersection

Chapter 28

Theme:
Font Size:
24px

“My brother was a brilliant inventor. He's no longer here to defend himself.”

Then he turned away.

I watched the interview from my office.

Nina stood beside me.

“He didn't answer the question,” she said.

“No.”

“Do you think he knew Mercer was coming?”

“I don't know.”

She looked at me.

“You're getting better at saying that.”

I almost smiled.

“Rebecca would be proud.”

Nina folded her arms.

“Adrian, can I ask you something?”

“Sure.”

“Are we still building a company?”

I turned toward her.

“What?”

“Because lately it feels like every decision revolves around Graham Sterling.”

I was quiet.

She continued.

“We have engineers waiting for approvals. Two major customers want demonstrations. The training division needs a budget decision.”

I looked down.

She softened her voice.

“I know this matters. I know your grandfather matters.”

I nodded.

“But Cross Meridian matters too.”

For several seconds, I didn't speak.

Then I looked at her.

“Schedule the executive team for Monday.”

She smiled faintly.

“Already did.”

I laughed.

“Of course you did.”

On Monday morning, I walked into the conference room and found twelve members of my leadership team waiting.

For months, I had been physically present at Cross Meridian while mentally living inside an investigation.

I had approved budgets.

Signed contracts.

Attended meetings.

But I hadn't been leading the way I once had.

I stood at the head of the table.

“Before we begin, I owe everyone an apology.”

The room became quiet.

“I allowed a personal legal matter to consume too much of my attention. Some of that was unavoidable. Some wasn't.”

Nina watched me from her seat.

I continued.

“I'm not abandoning the investigation. But I am changing how we manage it.”

I looked around the table.

“Rebecca and the independent investigators will handle the legal matters. Our security team will handle threats and evidence preservation. And I will focus on the company we built.”

Our chief engineer, David Chen, raised his hand.

“Does that mean we can finally approve the emergency communications demonstration?”

I smiled.

“Yes.”

He grinned.

“Then I forgive you.”

The room laughed.

For the first time in weeks, the sound felt normal.

That afternoon, we reviewed a new emergency response platform designed to maintain communications when ordinary networks were damaged.

It used multiple communication paths.

Cellular connections.

Radio links.

Satellite backups.

Local relay nodes.

And automated routing that could shift traffic when one path failed.

The system wasn't designed to give any single person unlimited control.

Its security architecture required separate authorization for sensitive operations.

No one administrator could silently redirect an entire emergency network.

As David explained the safeguards, I thought about my grandfather's note.

The real design was never about tracking vehicles.

It was about who could control the network when everything else failed.

I raised my hand.

“David, what happens if the central coordination service becomes compromised?”

He nodded toward the screen.

“The regional nodes continue operating independently.”

“And if an administrator tries to override them?”

“Requires separate authorization.”

“How many?”

“Two, from independent roles.”

I leaned forward.

“Can the system be configured so that emergency operators retain local control during a central failure?”

David smiled.

“That's the core design principle.”

I stared at the diagram.

For a moment, I felt my grandfather standing beside me.

Not literally.

But in the question.

In the purpose.

In the refusal to build a system that could be controlled by a single powerful person.

The laboratory called on Wednesday.

The technician, Dr. Miriam Cho, sounded cautiously optimistic.

“We've recovered a portion of the data.”

I stood.

“How much?”

“Enough to identify the structure.”

“What is it?”

“Technical records. Software instructions. Test logs. Some design documentation.”

I swallowed.

“Can you read them?”

“Some. Others require additional reconstruction.”

I looked toward the window.

“Is there anything about Thomas Cross?”

“Yes.”

My heart accelerated.

“What?”

“His name appears in the authorship records.”

I closed my eyes.

“And Walter Sterling?”

“Yes.”

I took a breath.

“Both?”

“Yes.”

She paused.

“But there's something unusual.”

I opened my eyes.

“What?”

“The module contains two separate design branches.”

I stared at the phone.

“Two versions?”

“Yes.”

“One labeled commercial. The other labeled continuity.”

I felt my pulse quicken.

“What does continuity mean?”

“We haven't completed the technical analysis.”

I nodded.

Then she said, “Mr. Cross, the continuity branch contains a document that appears to be a warning.”

I gripped the desk.

“A warning?”

“Yes.”

“About what?”

She hesitated.

“About centralized override authority.”

Two days later, I sat in a secure conference room with Rebecca, Marcus Reed, Dr. Cho, and an independent communications engineer named Professor Alan Whitaker.

A large screen displayed the recovered files.

Dr. Cho began carefully.

“The module appears to contain an early prototype architecture for a resilient emergency communications network.”

I nodded.

“The commercial branch focuses on vehicle location, dispatch coordination, and emergency signaling.”

She changed slides.

“The continuity branch addresses a different problem.”

Professor Whitaker leaned forward.

“How a network maintains operation when its central controller fails or becomes untrustworthy.”

I felt a chill.

He continued.

“The design proposes independent local nodes capable of maintaining emergency communications without relying on a single central authority.”

I stared at the diagram.

“That's remarkably advanced for 1989.”

Whitaker nodded.

“The concept was not unique, but this particular implementation is interesting.”

Rebecca asked, “Does it establish that Thomas Cross invented the system?”

Whitaker shook his head.

“Not by itself. The recovered files identify contributions, but we'd need to evaluate authorship, dates, and corroborating records.”

I nodded.

“Understood.”

Dr. Cho displayed another document.

“This is the warning.”

The title read:

CONTINUITY ARCHITECTURE — SECURITY CONCERNS

Below it appeared two names.

THOMAS CROSS

WALTER STERLING

I leaned forward.

The document described the danger of giving one administrator unrestricted authority to redirect emergency communications.

It warned that a compromised central controller could misroute messages, suppress alerts, or interfere with coordination during a crisis.

The proposed solution required independent authorization and local fallback capability.

I stared at the page.

It was the same principle we'd built into Cross Meridian's modern platform.

News in the same category

Cops Forced a Man’s Red Sports Car Off the Road — Then Five Black SUVs Surrounded the Intersection

45 Part