Chapter 3: The List of Five
For one long second, the reception hall seemed to tilt.
Not literally.
The floor remained level. The chandeliers continued shining. Conversations rose and fell around us, and a waiter passed with a tray of sparkling water as though nothing extraordinary had happened.
But Mitchell had just told me someone had placed my name on a list connected to an investigation he claimed to know nothing about.
I kept my voice steady.
“What list?””
He looked toward the nearest doorway.
“Not here.””
“Then where?””
“Somewhere private.””
“No.””
His eyes snapped back to mine.
“Sloane, please.””
The word surprised me.
In three years of marriage, Mitchell had issued instructions, offered opinions, and delivered the occasional apology when one of his jokes landed badly.
He had rarely pleaded.
I studied him carefully.
“Who called you?””
“My commanding officer.””
“What did he say?””
“That I needed to report to headquarters.””
“Why?””
“He wouldn't explain over the phone.””
“Then how do you know my name is on a list?””
Mitchell rubbed his palm against the side of his uniform trousers.
“Because he told me.””
“Which list?””
He glanced around again.
“Stop asking questions.””
The old reflex stirred inside me.
The desire to make the conversation easier. To soften my tone. To reassure him that I wasn't trying to cause trouble.
I swallowed it.
“I'm not asking you to disclose classified information,” I said.
“I'm asking why you brought up an operation you claim not to know anything about, and why you suddenly seem afraid of my work.””
He stared at me.
Then he leaned closer.
“Because I know how these things work. Someone makes a mistake, someone gets blamed, and careers disappear. You think the President shaking your hand protects you? It doesn't.””
“I never said it did.””
“Then stop acting invincible.””
“I don't.””
“You walked into that room like you owned it.””
“I walked into a room where I had been invited.””
His jaw flexed.
“You always do this.””
“Do what?””
“Make everything about principle. Rank. Duty.
Rules. You never think about the people caught in the middle.””
I looked at him for a long moment.
“Is that what this is about, Mitchell? People caught in the middle?””
He didn't answer.
A door opened behind us.
Admiral Whitaker stepped into the reception area with Deputy Security Director Bennett beside him.
Whitaker spotted us immediately.
“Colonel Merrick.””
I turned.
“Sir.””
His gaze shifted to Mitchell.
“Colonel Ashcroft.””
“Admiral.””
Bennett held out a hand.
“Colonel Merrick, I need you to accompany me.””
Mitchell stepped forward.
“What's happened?””
Bennett's expression remained neutral.
“That's not a discussion for this location.””
“I'm her husband.””
“And Colonel Merrick is part of an active security inquiry.””
His face tightened.
“An inquiry into what?””
“Colonel,” Whitaker interrupted, “you should report to your commanding officer as instructed.””
Mitchell went silent.
The admiral's tone wasn't threatening.
It didn't need to be.
I followed Bennett through a side corridor and into a secure room where a technician sat behind two monitors.
On the table lay the documents we'd reviewed earlier.
Beside them was a printed list of five names.
Mine was at the top.
Underneath it were the names of four other officers with authorized access to the contingency-routing archive.
I read them slowly.
Colonel Sloane Merrick.
Brigadier General Warren Pike.
Major General Daniel Reeves.
Colonel Anthony Bell.
Lieutenant Colonel Peter Shaw.
Five people.
Five accounts.
Five possible points of access.
Bennett tapped the page.
“This list was recovered from an encrypted file associated with an unauthorized export request. The request was blocked before the full archive could be copied.””
“Who created the file?””
“We don't know yet.””
“Was my account used?””
“An access token associated with your account was used to open the export request. That doesn't establish that you initiated it.””
“Where did the request originate?””
“The system registered a valid credential, but the location information is incomplete.””
“Then you don't know whether my account was compromised.””
“Correct.””
I exhaled slowly.
“Good.””
Bennett raised an eyebrow.
“Good?””
“It means we haven't confused a suspicious record with a conclusion.””
She studied me, then nodded.
“That's exactly why I wanted you in the room.””
The technician turned one monitor toward us.
A sequence of access events appeared on the screen.
“Look at the timestamps,” he said.
I leaned forward.
The first event had occurred at 0214.
The second at 0317.
The third at 0214 again.
The fourth at 0317.
And the export request had been initiated at 0214 the previous night.
I pointed at the screen.
“Those times aren't random.””
“What do you think they represent?”” Bennett asked.
“Shift transitions.””
The technician nodded.
“That was our initial theory.””
“Not just shift transitions,” I said.
“The archive generates automated backup checks at those intervals. Whoever made these changes knew when the system was busy processing routine maintenance.””
Bennett leaned over my shoulder.
“Would that make the activity harder to detect?””
“It could make an unauthorized action blend into the normal system traffic. But we'd need a technical review to confirm whether that happened here.””
The technician began typing.
“There's another issue,” he said.
“The export request referenced a contingency package that was scheduled to remain inactive until next month.””
I felt a chill move through me.
“That package contains the alternate distribution routes.””
“Yes.””
“Routes that haven't been activated?””
“Correct.””
I looked at Bennett.
“If someone obtains those routes before activation, they could predict where supplies are supposed to go if the primary network fails.””
“And redirect them,” she said.
“Or make sure they never arrive.””
The room fell silent.
I thought of the fourth shipment.
The one recorded as delivered.
The one that had never reached the receiving facility.
It had seemed like a clerical discrepancy when I first saw it.
Now it looked like a rehearsal.
Bennett closed the folder.
“We're going to need a formal statement from you.””
“You'll have it.””
“And I need you to tell me whether anyone outside the authorized group has ever asked about the contingency package.””
I considered her question.
Then I remembered a conversation from six weeks earlier.
I had been sitting in the kitchen at home, reviewing an unclassified personnel document. Mitchell had walked in, poured himself a glass of water, and glanced at the page.
“Busy night?”” he'd asked.
“Always.””
“Anything interesting?””
“Nothing I can discuss.””
He'd smiled.
“Of course not. National secrets. Meanwhile, I can't even get you to tell me what we're having for dinner.””
I had laughed despite myself.
He had leaned against the counter.
“You know, logistics isn't exactly mysterious. Routes, warehouses, fuel, schedules. Move things from A to B.””
“Sometimes.””
“What makes your work so different?””
I had looked up.
“Because sometimes A is under attack, B is inaccessible, and the things we're moving are the only reason people survive long enough to be evacuated.””
He'd gone quiet.
For a moment, I thought he'd finally understood.
Then he had smiled and said, “You should put that on a presentation. People might actually pay attention.””
I returned to the present.
Bennett was waiting.
“My husband has asked general questions about my work,” I said.
“I've never provided classified information. I can't recall him asking about the contingency package specifically.””
“Has he ever seen the archive?””
“No.””
“Your credentials?””
“No.””
“Any printed material?””
“No.””
She nodded.
“That's useful.””
I gave my statement.
We spent the next hour documenting my access history, confirming the dates of the suspicious routing changes, and identifying every official who had received the authorized contingency package.
The process was meticulous.
It was also necessary.
At 11:42 p.m., the technician discovered something that made him stop typing.
“Deputy Director?””
Bennett approached the screen.
“What is it?””
“The export request was blocked, but the system generated a temporary recovery file before the security rule stopped it.””
“How much data was recovered?””
“Not the full package. A partial index.””
“What does the index contain?””
“File names, authorization references, and a list of the accounts associated with the archive.””
Bennett leaned closer.
“Can we establish where it was sent?””
“We're tracing that now.””
I looked at the monitor.
“Does the partial index contain the list of five?””
“Yes.””
“Then whoever created the export request may have wanted more than the routes.””
Bennett turned toward me.
“What else?””
“The identities of the people who could authorize them.””
The technician stopped typing again.
He clicked into a second window.
“Deputy Director, we have a destination.””
Bennett stepped beside him.
“Where?””
“An external relay. The connection was routed through several systems, but the last authenticated access came from a government network.””
“Which network?””
He hesitated.
Then he opened a detail panel.
I saw the department designation first.
Then the installation code.
Then the unit identifier.
My stomach tightened.
I knew that code.
I had seen it on the envelope Mitchell received in the reception hall.
It belonged to the command where my husband was currently assigned.
I forced myself to read the record again.
The identifier was unmistakable.
Bennett looked at me.
“Colonel Merrick, do you recognize this installation?””
“Yes.””
“From where?””
“My husband's current command assignment.””
She didn't react.
“Does Colonel Ashcroft have authorized access to your contingency archive?””
“No.””
“Does his command have any legitimate reason to receive this package?””
“Not through the channel shown here.””
The technician turned back to his keyboard.
“There's more.””
He opened the access details for the external relay.
A user credential appeared.
The name was partially obscured, but the account designation remained visible.
Bennett leaned forward.
“Can you recover the full identity?””
“I'm trying.””
The screen flickered as the system loaded another record.
Then the technician went very still.
“What?”” Bennett asked.
He swallowed.
“The relay was accessed using credentials associated with a senior officer's office.””
“Whose office?””
He turned the screen toward us.
The name appeared in black letters.
*BRIGADIER GENERAL WARREN PIKE.*
I stared at it.
Pike was one of the five people on the list.
He was also the officer who had asked for simplified contingency-routing summaries three weeks earlier.
The coincidence was becoming difficult to ignore.
Bennett immediately contacted the security team.
“Preserve the access records. Restrict the account. Notify the authorized investigator. Do not contact the office directly until we've confirmed the authentication trail.””
The technician nodded.
I sat back in my chair.
“Does this prove Pike initiated the export?””
“No,” Bennett said.
“It proves credentials associated with his office were used at the relay. We still need to establish who controlled those credentials and whether the activity was authorized.””
I appreciated the distinction.
But my mind had already moved to Mitchell.
He had known about the Eastern Corridor.
He had asked about the supply problems.
He had received a sealed letter from his own command.
And he had warned me that my name was on a list before anyone in this room had told him it existed.
I looked at Bennett.
“Can I ask you something?””
“Of course.””
“If my husband received a direct order from his commanding officer tonight, would that order necessarily relate to this inquiry?””
“Not necessarily. We can't infer the contents of a communication we haven't reviewed.””
“Could his command have contacted him because of this relay?””
“Possibly. But we need evidence before we connect the two.””
I nodded.
That was the answer I expected.
It wasn't the answer I wanted.
At 12:18 a.m., Bennett escorted me to a private office where I could call my designated command contact.
I gave a brief status report, confirmed that I had not disclosed restricted information, and requested preservation of the archive logs.
When I ended the call, my personal phone showed three missed calls from Mitchell.
Then a text message appeared.
*We need to talk before you make a mistake you can't undo.*
A second message followed.
*I didn't know what they were doing. I swear.*
I read it twice.
I hadn't accused him of doing anything.
I hadn't even told him what we'd found.
My thumb hovered over the screen.
Then another message arrived.
*Sloane, please. There is something you need to know about General Pike.*
I typed a single question.
*What does General Pike have to do with you?*
The typing indicator appeared.
Disappeared.
Appeared again.
Finally, Mitchell sent a photograph.
It showed a document lying on a desk. The image was slightly blurred, as though it had been taken in a hurry.
At the top was the heading for an internal command review.
Below it were several lines of text.
One sentence was highlighted.
Colonel Mitchell Ashcroft is to report for immediate questioning regarding his contact with Brigadier General Warren Pike and the unauthorized transfer of contingency-routing information.
I read it again.
Then I enlarged the photograph.
At the bottom of the page was a list of attached exhibits.
The first was a communications log.
The second was a system access report.
The third was a financial record.
I stared at the third line until the letters seemed to blur.
Because the financial record did not list General Pike.
It listed Mitchell.
And beside his name was a payment date from six weeks earlier.
The exact week he had asked me what made my work so different.
My phone vibrated again.
This time, Mitchell called.
I answered.
Neither of us spoke for several seconds.
Then he said, “Sloane, I can explain the money.””
I gripped the edge of the desk.
“What money?””
His breath caught.
“You saw the attachment.””
“I'm looking at a photograph of a document that accuses you of unauthorized contact with General Pike.””
“It's not what it looks like.””
“Then tell me what it is.””
He went silent.
In the background, I heard a door close and the muffled sound of someone speaking.
When Mitchell finally answered, his voice had dropped to a whisper.
“Six weeks ago, Pike told me he needed help identifying a leak inside the command. He said he couldn't trust the official channels. He asked me to review a few records because I had experience with operational planning.””
“You told me you weren't involved in the Eastern Corridor.””
“I wasn't supposed to be.””
“That's not an answer.””
“I never gave him your plans.””
“Then why is your name attached to a payment record?””
He didn't respond.
I closed my eyes.
For three years, I had defended Mitchell when other people questioned his character. I had explained his jokes, softened his arrogance, and told myself that a good man could be careless with someone else's dignity without intending to cause harm.
But this was different.
This wasn't a joke at a dinner table.
This was an investigation involving compromised military information, missing supplies, and people whose lives depended on accurate planning.
“Mitchell,” I said, “I need the truth.””
“I was paid to review documents.””
“By whom?””
“Pike's office.””
“Why?””
“He said it was consulting work related to an internal review.””
“You're an active-duty colonel. What kind of consulting work?””
“I didn't know it was connected to your operation.””
“Did you sign anything?””
A pause.
“Yes.””
“What?””
“A confidentiality agreement.””
“Did you send him information?””
“Only what he requested.””
My fingers tightened around the phone.
“What did he request?””
Mitchell inhaled shakily.
“Names, Sloane.””
“Whose names?””
“The people with access to the contingency archive.””
The room seemed to grow smaller.
“Did you know what the archive contained?””
“No.””
“Did you know the list was connected to the supply diversions?””
“No.””
“Did you ask?””
His silence answered before he did.
“No,” he whispered.
I stared at the photograph on my screen.
“You were paid to provide the names of officers with access to my operation, and you never asked why?””
“I thought it was a routine security review.””
“You thought?””
“I trusted Pike.””
“And you expected me to believe that?””
“I'm telling you the truth.””
“Then give the investigators every document, every message, and every payment record. Don't delete anything. Don't contact Pike. Don't discuss this with anyone who hasn't been authorized to handle the inquiry.””
“Sloane—”
“Do you understand?””
He swallowed.
“Yes.””
I ended the call.
For a moment, I sat perfectly still.
Then I forwarded the photograph to Deputy Director Bennett through the approved channel and requested that the image be preserved as evidence.
Her reply arrived less than a minute later.
*Do not contact Colonel Ashcroft again about the investigation. We will arrange a formal interview.*
I placed the phone on the desk.
Outside the office, footsteps moved along the corridor.
The White House was quieter now. The ceremony was over. The guests were leaving. Somewhere in the building, the President was preparing for the next day.
I had arrived that evening expecting to discuss supply routes, emergency distribution plans, and a possible breach of the contingency archive.
Instead, I had discovered that my husband had accepted money to identify the people who could access my work.
He might not have understood what he was helping someone do.
He might not have known the money was connected to the diversions.
He might even have believed he was helping a senior officer investigate a legitimate security concern.
But none of those possibilities changed the fact that he'd made a decision without asking the questions his duty required him to ask.
And now the investigators had a reason to question him.
My phone vibrated one final time.
A message from an unknown number.
No name.
No signature.
Just a photograph of the same five-name list we'd recovered from the export request.
Someone had circled my name in red.
Beneath it, a single sentence appeared.
*PIKE ISN'T THE PERSON YOU NEED TO BE AFRAID OF.*
I stared at the message.
May you like
Then another line appeared.
*ASK YOUR HUSBAND WHO REALLY SIGNED THE AGREEMENT.*
