Chapter 8: The General Who Never Looked at Me
General Daniel Reeves arrived at the security facility at 8:00 a.m. the following morning.
He came without an aide.
His uniform was immaculate, his expression composed, and his posture so perfectly controlled that I could have mistaken him for a photograph of an officer rather than a man walking into an investigation that might end his career.
I had seen him at the White House ceremony.
He had congratulated me after the briefing, praised the efficiency of my team, and told me that the military needed more officers who understood the difference between a plan and a promise.
At the time, I'd taken it as a compliment.
Now I wondered whether he'd been measuring how much I knew.
Bennett met him in the lobby.
I watched through the glass as she greeted him and escorted him toward the interview rooms.
Reeves glanced toward the operations wing.
For a brief moment, our eyes met.
He didn't smile.
He didn't look away.
He simply inclined his head, as if acknowledging a colleague in a hallway.
Then he disappeared through the door.
I returned to my desk.
At 8:37 a.m., Bennett called.
“Colonel, I'd like you to join us for part of the interview.””
“Why?””
“General Reeves has agreed to answer questions about the authorization email and the Meridian payment. He has also requested that you explain the operational significance of the archive.””
“Is that appropriate?””
“Yes. You'll be present as the technical lead, not as an investigator.””
“I understand.””
When I entered the interview room, Reeves was seated at the table with his hands folded in front of him.
He stood.
“Colonel Merrick.””
“General.””
He gestured toward the chair opposite him.
“Please.””
Bennett remained beside the recorder.
“General Reeves, we're going to continue the interview regarding the authorization email sent to Meridian Strategic Advisory and the subsequent export attempt involving the contingency-routing archive.””
Reeves nodded.
“I understand.””
Bennett turned to me.
“Colonel, please explain what the archive contains and why access is restricted.””
I gave a concise explanation.
“The archive contains approved contingency options for emergency distribution. It includes alternate routing plans, resource dependencies, and authorization references. Access is restricted because premature disclosure could allow an adversary to predict how we would respond if a primary route became unavailable.””
“Would an administrative review require access to that information?”” Bennett asked.
“Not necessarily. A review could examine authentication records without exposing the underlying routes, provided the system administrator established the appropriate permissions.””
Reeves nodded.
“That was my understanding.””
I turned toward him.
“Then why did your office authorize a review that requested personnel names and asked whether the archive could be accessed without triggering an alert?””
His expression didn't change.
“My office did not authorize that request.””
“An email from your office says otherwise.””
“I've seen the email. It appears to have originated from a legitimate account, but I did not send it.””
“Did you authorize someone else to send it?””
“No.””
“Did you know Mitchell Ashcroft was being paid by Meridian?””
“I learned of the payment yesterday.””
“Did you know he had provided the names of officers with access to the archive?””
“No.””
“Did you know Eleanor Ashcroft had arranged the meeting?””
For the first time, Reeves hesitated.
“I know Mrs. Ashcroft socially.””
“How?””
“She served on the board of a charitable organization that supported military families. I met her at several events.””
“Did she discuss Mitchell's career with you?””
“Not in any substantive way.””
“Did she ever ask you to help him obtain a promotion?””
Reeves looked directly at me.
“No.””
Bennett made a note.
I studied his face.
He seemed genuinely offended by the question.
That didn't prove he was innocent.
It only meant he understood how to perform indignation.
Bennett continued.
“General, the financial records show that Meridian received funds through Northbridge Risk Partners shortly before the consulting agreement was created. Do you have any relationship with that company?””
“Not currently.””
“Did you have one in the past?””
“I attended a professional conference where one of its former directors presented. That was several years ago.””
“Did you approve any payment to Meridian?””
“No.””
“Did you approve the dormant procurement code that appears on the invoice?””
“No.””
Bennett placed the invoice on the table.
Reeves studied it.
“That code should not have been active.””
“Can you explain why it was used?””
“No.””
“Who had authority to reactivate it?””
“Several administrative officers could have initiated a request. Final approval required independent verification.””
“Do you know whether that verification occurred?””
“No.””
He looked at me.
“Colonel, I want to be clear about something. If someone used my office to authorize an improper review, I want that person identified as much as you do.””
I held his gaze.
“Then I hope your records help us find them.””
The interview continued for another twenty minutes.
Reeves denied authorizing the agreement, denied instructing Mitchell to provide the personnel list, and denied knowing that the archive had been targeted.
He agreed to surrender relevant communications and permit a review of the account associated with the authorization email.
At the end, Bennett asked whether he had any additional information.
Reeves paused.
“Yes,” he said.
“There is one thing.””
Bennett leaned forward.
“What?””
“Three weeks ago, I received a request from an intermediary claiming to represent the White House. The person asked whether Colonel Merrick had access to the contingency archive and whether she would be attending the upcoming ceremony.””
My pulse quickened.
“What did you say?”” I asked.
“I said that I couldn't discuss your access permissions. I also said I had no information about your attendance.””
“Did you identify the intermediary?””
“No. The request came through an administrative channel that appeared legitimate.””
“Do you still have it?””
“Yes.””
Bennett made a note.
“Please provide it to the investigators.””
“I will.””
The interview ended.
Reeves stood and adjusted his jacket.
As he reached the door, he turned toward me.
“Colonel, I hope you understand that a person's name appearing on a record doesn't establish responsibility.””
“I do, General.””
“Good. Because I suspect someone has been very careful about whose names appear where.””
Then he left.
I remained seated.
Bennett closed the file.
“What do you think?””
“He could be telling the truth.””
“And?””
“He could also be withholding information.””
She gave a small nod.
“That's where we are.””
I returned to the operations room.
At 10:14 a.m., the investigators recovered the original authorization email from Reeves's account archive.
The message had been sent at 11:47 p.m. six weeks earlier.
The sender's account was legitimate.
The device identifier was not.
The message had been created on a workstation registered to the office of the Assistant Secretary for Defense Logistics.
I stared at the report.
“Who had access to that workstation?””
“Several staff members,” the investigator replied.
“We're narrowing it down.””
“Could someone have used it while the assistant secretary was away?””
“Yes.””
“Was the workstation physically accessed that night?””
“Badge records show a single entry into the office suite shortly before midnight.””
“Who entered?””
He opened the next page.
The badge belonged to Lieutenant Colonel Peter Shaw.
I leaned forward.
“Shaw was assigned to security at the White House ceremony.””
“Correct.””
“Was he assigned to the assistant secretary's office six weeks ago?””
“Temporarily. He was coordinating a document transfer.””
The pattern was becoming clearer.
Shaw had access to the office where the authorization email originated.
He had been assigned to the White House ceremony.
He had access to the contingency archive.
And he had been present in the same building where the President had publicly recognized me.
But I still didn't know why.
“Has Shaw been interviewed?”” I asked.
“His interview is scheduled for this afternoon.””
“Good.””
The investigator left.
I opened the guest list again.
Shaw's name appeared beneath the security detail designation.
The unknown sender had told me to check the guest list.
Perhaps the purpose had been to reveal Shaw.
Or perhaps it had been to reveal someone else.
I searched the list for every attendee associated with the assistant secretary's office.
Three names appeared.
One belonged to a civilian aide.
One belonged to a military liaison.
The third belonged to a woman who had signed off on the temporary workstation access.
*Eleanor Ashcroft.*
I stared at the name.
Then I opened the accompanying attendance record.
Eleanor had attended a charitable reception at the same government complex three weeks before the White House ceremony.
The event had been sponsored by a military family foundation.
The guest list included several senior officials, their spouses, and representatives from private contractors.
Meridian Strategic Advisory had been represented by Dr. Vivian Cross.
Northbridge Risk Partners had been represented by a former intelligence officer.
And Eleanor had signed in beside both of them.
I called Bennett.
“Eleanor wasn't merely connected to Mitchell's introduction to Meridian.””
“What did you find?””
“She attended an event with Cross and a representative of Northbridge Risk Partners. The same company involved in the payment chain.””
Bennett was silent for a moment.
“Send me the records.””
I did.
Within minutes, she arrived at my desk.
“That's a stronger connection,” she said.
“But we still need to establish whether they discussed the agreement.””
“Agreed.””
She studied the guest list.
“There's something else. The former intelligence officer representing Northbridge is named Victor Hale.””
“Does he have a connection to General Reeves?””
“They worked on a security modernization project years ago. Hale left government service and joined the private sector.””
“Could he have arranged the payment?””
“Possibly.””
I pointed to the date.
“The event took place three weeks before the agreement was created.””
“Which gives us a potential timeline.””
Bennett took out her phone.
“I'm requesting an interview with Hale.””
Before she could finish the call, an investigator hurried into the room.
“Deputy Director, we have a problem.””
“What happened?””
“Lieutenant Colonel Shaw's interview has been postponed.””
“By whom?””
“His commanding officer. Shaw reported a medical emergency and was transported to a military clinic.””
Bennett's expression tightened.
“Is he injured?””
“We don't know yet. The report says he became ill shortly after arriving for the interview.””
“Where is he now?””
“Under observation.””
“Secure his devices. Preserve his access credentials. No one interviews him until the medical team clears him.””
The investigator nodded and left.
I stared at the screen.
“Do you think he's avoiding the interview?””
“I think we need to establish what happened before we speculate.””
She turned toward me.
“Colonel, I want you to review the archive's authentication logs again. Look for any activity associated with Shaw's account before the first diversion.””
“I'll do it.””
For the next hour, I examined every available record.
At first, the pattern looked ordinary.
Shaw's account had accessed the archive several times over the previous month. Most entries corresponded to scheduled reviews or routine system checks.
Then I noticed an unusual sequence.
Three days before the first shipment diversion, Shaw's account had opened a document that wasn't part of his assigned responsibilities.
The document contained a list of authorized contingency reviewers.
The same five names.
My name at the top.
The file had been opened at 2:14 a.m.
The session had lasted exactly three minutes.
Then the record disappeared from the standard activity summary.
Not deleted.
Reclassified.
The file had been moved into a restricted administrative category that ordinary users couldn't view.
I called Bennett.
She came over immediately.
“Can we recover the original classification record?”” she asked.
“Yes. The archive retains a change history.””
I opened the audit trail.
The classification change had been approved by an account associated with the Assistant Secretary for Defense Logistics.
But the approval had been made using a temporary delegation token.
A token issued to an office that no longer existed.
The same dormant procurement channel that appeared on the invoice.
Bennett leaned closer.
“Someone is reusing old authorization pathways.””
“Or someone never deactivated them.””
“Can we establish who initiated the change?””
“Not yet. The originating session is incomplete.””
She looked at the screen.
“Preserve the logs. We need a forensic copy.””
I exported the approved audit records and sent them to the investigators.
Then I returned to the document.
Five names.
One list.
One archive.
One attempt to make a suspicious action appear legitimate.
I had been staring at the names for so long that I almost missed the small note beneath the final entry.
A reference to an administrative review.
And beside it, a short identifier.
*PROJECT NIGHTGLASS.*
I had never seen that name before.
I searched the authorized records.
No result.
I searched the approved project index.
Nothing.
I searched the archive's historical catalog.
Still nothing.
Then I tried the identifier associated with the dormant procurement channel.
The system returned one record.
Not a project file.
A contract closure notice.
It was dated two years earlier.
The notice stated that Project Nightglass had been terminated following a review of unauthorized access to government logistics systems.
I read the document twice.
The project had been closed.
Its access credentials should have been revoked.
Its procurement code should have been deactivated.
And yet both had appeared in the records associated with the current breach.
I called Bennett.
“Project Nightglass.””
She was silent.
“Where did you find that name?””
“In the archive's classification history. It's connected to the dormant procurement channel.””
“Send me the record.””
I did.
She read it, then closed her office door.
“Sloane, I need you to understand that this may be a separate historical matter. We can't assume the current breach is connected simply because an old project identifier appears in the records.””
“I agree.””
“But if the project was terminated because of unauthorized access, we need to establish whether the same individuals were involved.””
“Do we know who led it?””
Bennett opened the closure notice.
The leadership section was partially redacted.
Only one name remained visible.
*PROJECT DIRECTOR: VICTOR HALE.*
The former intelligence officer from Northbridge Risk Partners.
The man who had attended the charitable reception with Eleanor and Dr. Cross.
The man whose company had received the funds that eventually reached Meridian.
I stared at the name.
“That's our connection.””
“It's a connection,” Bennett corrected.
“We still need to establish what it means.””
She picked up her phone.
“Find Victor Hale. Confirm his location and request a formal interview. Preserve every record associated with Project Nightglass.””
She ended the call.
I returned to my desk.
For the first time, I could see a possible shape to the operation.
Someone had used an old project, an inactive authorization channel, and a chain of private companies to create the appearance of a legitimate security review.
Mitchell had provided the personnel names.
Eleanor had arranged the introduction.
Dr. Cross had accepted an authorization she hadn't independently verified.
General Reeves's account had been used to approve the request.
And Shaw's access records placed him at the workstation where the authorization originated.
But I still couldn't tell whether they were all part of the same scheme, whether some had been deceived, or whether the entire chain had been designed to conceal one person's actions.
At 12:52 p.m., Bennett called me into her office.
A new message had arrived from the unknown sender.
It contained no text.
Only a scanned document.
The header read:
*PROJECT NIGHTGLASS — FINAL AUTHORIZATION*
Beneath it were two signatures.
One belonged to Victor Hale.
The other belonged to a senior government official whose name had been blacked out.
But the signature was unmistakable.
I'd seen it on the President's briefing documents.
I'd seen it on the official approval for my White House assignment.
I'd seen it on the order that authorized the contingency archive's creation.
The signature belonged to the official who had approved my appointment to the operation.
The person who had personally recommended that the President recognize my work.
Admiral Thomas Whitaker.
I looked up at Bennett.
“Has Admiral Whitaker seen this?””
“Not yet.””
“Then we need to show him.””
Bennett studied the document.
“Yes,” she said quietly.
“We do.””
May you like
And for the first time since the investigation began, I wondered whether the person who had welcomed me into the White House had been protecting me from the breach.
Or protecting the breach from me.
