Chapter 8 - The Name in the File

The hospital room smelled of antiseptic, fresh linen, and the burnt coffee someone had left outside the nurses' station.
I lay propped against two pillows, my right arm supported in a sling, while a physician reviewed the results of my examination.
The X-rays showed no fracture. My shoulder injury appeared to involve soft tissue, though the doctor wanted me to follow up if the pain worsened. My wrists were bruised and swollen, and several small cuts on my face required cleaning.
Nothing was life-threatening.
That was the good news.
The bad news was that I could not stop replaying the afternoon.
Garrett's voice.
The baton striking the hood.
The sharp click of his gun leaving its holster.
The look on Miles's face when he realized that his partner might actually shoot Ruth.
I had spent years telling other people that traumatic events could continue affecting them long after the immediate danger had passed.
Now I understood the truth of that advice in a more personal way.
My body was safe.
My mind was still on the highway.
At 6:18 p.m., Daniel Mercer arrived with two federal investigators.
He carried a thin folder and wore the same dark suit he had worn at the operations center.
He looked exhausted.
"How are you feeling?" he asked.
"Like I lost an argument with a truck."
He almost smiled.
"That's one way to describe it."
He pulled a chair beside the bed.
The two investigators introduced themselves. Special Agent Lena Brooks was in her early forties, with short black hair and a direct manner. The second investigator, Thomas Reed, was a forensic specialist who carried a laptop and a small case of equipment.
"We've secured the initial dispatch audio," Lena said. "We're also working to preserve both body-camera recordings and the patrol vehicle's data."
"Has anyone accessed the footage?"
"We're reviewing the audit trail now."
"That isn't an answer."
Lena nodded.
"You're right. We have evidence that someone attempted to access the incident records after the stop. We don't yet know whether any files were opened, copied, or altered."
"Who had access?"
"That's part of the investigation."
I looked at Daniel.
"Have you identified the person who accessed my travel authorization?"
"We have a name associated with the original request," he said. "Deputy Chief Owen Rusk."
"And the second access attempt?"
"We're still tracing it."
"Using whose credentials?"
He hesitated.
"Mine."
I stared at him.
"You already told me that."
"The system recorded a second access using my credentials at 4:34 p.m. I was in the operations center, but I didn't initiate it."
"Could someone have used your account remotely?"
"Possibly. We're examining the authentication records."
I turned toward Lena.
"Is there any evidence that Garrett knew my route before he stopped me?"
"Not yet."
"Then I want that question treated as a priority."
"It is."
I took a breath.
"Good. Because I want to be clear about something. I am a victim of this incident, but I also have information that may be relevant to the investigation I was conducting. I don't want the two matters confused."
Daniel leaned forward.
"Renata, you need to rest."
"I will. After I understand what we're dealing with."
He looked at Lena.
She opened the folder.
"We've reviewed the initial case materials you submitted this morning. Your operation involved allegations of improper handling of public safety grant funds, correct?"
"Yes."
"Specifically, funds allocated to rural emergency response programs."
"Correct."
"Your team identified discrepancies in several county contracts. Some of the discrepancies involved invoices for equipment that may never have been delivered."
I nodded.
"That was one of the issues."
"And a portion of the contracts involved Ashford County."
"Yes."
Lena glanced at Daniel.
"There's something else."
She placed a printed document on the table beside my bed.
It was a summary of the original route authorization.
I recognized the document immediately.
The route had been generated from my approved travel plan, with the destination listed as my residence and the expected arrival window included. The information was restricted because the operation involved sensitive interviews and confidential records.
Someone had requested access to that document the previous afternoon.
The request had been denied.
But the system log showed that the same account had attempted to access a related file approximately twenty minutes later.
"Why wasn't I informed?" I asked.
"Your supervisor was notified of the denied request," Lena replied. "The follow-up request was flagged for review, but it hadn't yet been escalated."
"Who reviewed it?"
"A security analyst. The analyst determined that the request lacked sufficient authorization."
"Did anyone contact Rusk?"
"No."
"Why not?"
"We're still reviewing the decision."
I looked at the document.
The request was signed electronically by Deputy Chief Owen Rusk.
His name appeared beneath a short explanation stating that the information was needed for interagency coordination.
I read it twice.
"That doesn't make sense."
"Why?" Daniel asked.
"Because I wasn't conducting an interagency operation. The county had no need to know my travel route."
"That was our initial assessment, too."
"Then why did the analyst consider the request routine?"
Daniel didn't answer.
I looked at Lena.
"Has Rusk been interviewed?"
"Not yet."
"Don't interview him until the access logs are secured and we know who else may have seen the request."
"Agreed."
She turned another page.
"This is where the investigation becomes more complicated."
The next document contained a list of county contractors associated with the grant program.
Several names were familiar from my earlier review.
One was not.
GARRISON STRATEGIC SERVICES, LLC.
The company had received multiple payments for security equipment and communications upgrades. Its registered office was listed at a commercial address in a neighboring county.
I scanned the payment amounts.
One invoice alone exceeded four hundred thousand dollars.
"Who owns this company?" I asked.
"On paper, a holding company registered in Delaware," Lena said. "The public filings identify a manager, but we've not yet established the beneficial ownership."
"Why is it included in the case file?"
"Because the payments appear in several disputed contracts."
I looked at the dates.
One payment had been issued three days before a county emergency communications system underwent an unscheduled upgrade.
Another had been approved the day after a deputy filed a report about an equipment malfunction.
The third was dated two weeks before a confidential witness withdrew a complaint involving alleged misconduct by a senior county official.
I felt the room grow colder.
"Daniel, pull the original interview notes."
He opened his laptop.
"Which interview?"
"The witness who mentioned the meeting with Rusk."
He searched the secure file repository.
A minute passed.
Then another.
Finally, he turned the screen toward me.
The witness's name had been redacted in the working copy, but I remembered the substance of the interview.
A former county procurement officer had reported that certain grant contracts were approved without the required competitive process. The officer had also described a meeting attended by Rusk and a private contractor whose identity the witness had been unable to confirm.
The contractor, according to the statement, had arrived carrying a folder marked with the words Route Security.
I read the passage again.
"Was this folder photographed?"
"No," Daniel replied. "The witness described it verbally."
"Did the witness identify the contractor?"
"Not by name."
"Did we follow up?"
"Yes. The witness declined a second interview."
"Why?"
"According to the case note, the witness was concerned about employment consequences."
I stared at the screen.
A person had described a suspicious meeting.
The person had refused further cooperation.
A county official had attempted to obtain my restricted travel information.
My vehicle's tracking system had stopped transmitting shortly after a deputy pulled me over.
And now the deputy had warned me that I should have stayed on a different road.
I had spent enough time investigating civil rights violations to know that a single suspicious fact rarely proved a conspiracy.
But several connected facts could establish a direction worth pursuing.
"Find the witness," I said.
"We're working on it," Lena replied.
"No. I want an immediate welfare check. The person may be in danger."
"We'll coordinate that through the appropriate channels."
"Independent channels," I added. "Not Ashford County."
Lena nodded.
Daniel closed the laptop.
"Renata, there is one more issue."
I looked at him.
"What?"
"The Phantom's security module transmitted a partial diagnostic packet before the signal disappeared."
"Thomas mentioned that."
"There's a timestamp attached to the final transmission. It indicates that the interruption began before the first confirmed report of damage to the vehicle."
I frowned.
"How long before?"
"Approximately twenty seconds."
The room seemed to contract around me.
"Are you saying the equipment may have been interfered with before Garrett struck the windshield?"
"We don't know what caused the interruption."
"Could it have been a communications failure?"
"Yes."
"Could it have been physical damage?"
"Possibly."
"Could someone have deliberately interfered with it?"
Daniel hesitated.
"That possibility hasn't been ruled out."
I looked at Thomas.
"Can you determine whether the module was jammed, disconnected, or damaged?"
"We can examine the recovered equipment and compare the stored telemetry with the network logs. We may be able to narrow it down."
"Then do it."
Thomas nodded.
Lena closed the folder.
"We should let you rest."
"One last question."
She stopped.
"Has anyone located the blue pickup visible in Ruth Okapor's video?"
Lena exchanged a glance with Thomas.
"We're working on that, too."
"Was the vehicle captured on another camera?"
"Yes."
I waited.
Lena's expression became more serious.
"A private roadside security camera recorded the pickup entering the area approximately six minutes before the stop. It appears to have left less than two minutes after the deputy began damaging your vehicle."
"Can you identify the driver?"
"Not yet."
"Then what do we know?"
She looked at the folder.
"The vehicle's registration appears to be associated with a company connected to one of the disputed county contracts."
I felt my pulse quicken.
"Which company?"
Lena turned the page and placed it in front of me.
The name was printed in bold letters.
GARRISON STRATEGIC SERVICES, LLC.
For several seconds, I could hear nothing but the soft rhythm of the hospital monitor.
The company that appeared in the disputed financial records had a vehicle near the scene of my detention.
The same scene where a deputy had destroyed my car, threatened a witness, and warned me that I should have taken another route.
I looked at Daniel.
"Tell me this is a coincidence."
He did not answer.
That was answer enough.
My phone vibrated on the bedside table.
A message had arrived from an unfamiliar number.
I picked it up.
There was no greeting.
No explanation.
Only a photograph.
The image showed my Phantom parked outside the federal building earlier that afternoon. I was visible through the windshield, seated behind the wheel.
Someone had taken the photograph from across the street.
Below it was a single sentence.
YOU WERE WARNED TO STAY OUT OF ASHFORD COUNTY.
I stared at the screen.
Daniel leaned closer.
"Where did that come from?"
"I don't know."
"Don't respond."
"I wasn't planning to."
He took a photograph of the message using his secure work phone, then instructed Thomas to preserve the original device data.
I read the sentence again.
I had never received a warning about Ashford County.
Not from my supervisor.
Not from the sheriff's office.
Not from anyone involved in the investigation.
But whoever had sent the message believed I had.
Or wanted me to believe it.
I looked up at Daniel.
"Someone is trying to frighten me away from this case."
"Yes."
"Why now?"
He studied the photograph.
"Because something changed today."
I thought of Garrett's expression when I asked who had told him about my route.
I thought of the blue pickup, the missing signal, and the attempted access to my travel authorization.
Then I remembered something else.
When I had first arrived at the federal building that morning, an administrative assistant had stopped me in the corridor and asked whether I had changed my travel plans.
I had assumed she was referring to a routine scheduling update.
I had said yes, explaining that I was taking a different route home.
She had nodded and returned to her desk.
At the time, the conversation had seemed meaningless.
Now it felt like a door opening onto a dark room.
"Daniel," I said, "who knew I changed my route this morning?"
He considered the question.
"Your supervisor, the transport coordinator, and anyone who had authorized access to your itinerary."
"And the administrative assistant who asked me about it?"
His expression sharpened.
"Who?"
I gave him her name.
He wrote it down.
Then he made a call to the operations center.
I watched his face as he listened.
At first, he looked merely concerned.
Then he became very still.
"Say that again," he told the person on the other end.
A long pause followed.
Finally, he ended the call.
"What is it?" I asked.
Daniel sat down slowly.
"The administrative assistant you mentioned hasn't been at work since noon."
"Did she call in sick?"
"No."
"Did anyone contact her?"
"Her supervisor tried. Her phone is going directly to voicemail."
I stared at him.
"That doesn't prove anything."
"No," he agreed. "It doesn't."
"But?"
He looked toward the hospital window, where the last light of evening was fading behind the buildings.
"But someone accessed her personnel file an hour ago."
I felt the familiar coldness settle in my chest.
"Who?"
Daniel turned back toward me.
"The request came from an account assigned to Deputy Chief Owen Rusk."
For a moment, neither of us spoke.
Then my phone vibrated again.
Another message.
This one contained no photograph.
Only six words.
ASK MILES WHAT HE SAW THAT DAY.
I read the sentence twice.
Miles Ansar.
The young deputy who had watched Garrett destroy my vehicle. The partner who had finally called for help. The man whose expression had changed when the tracking module stopped transmitting.
I looked at Daniel.
"Has Miles been interviewed?"
"Not yet."
"Then find him."
"We will."
"No," I said, sitting up despite the pain in my shoulder. "Find him now."
Daniel studied me.
"Renata, you're injured. You need to rest."
"I will rest when I know whether that young man is safe."
He held my gaze for several seconds.
Then he picked up his phone.
Outside the room, a nurse pushed a cart past the open doorway. Somewhere down the corridor, a child laughed, and a monitor sounded a steady alarm before a nurse silenced it.
Ordinary life continued around us.
But the investigation had changed.
It was no longer simply about a deputy who had abused his authority on a deserted highway.
It was about a restricted travel file, a missing employee, a private contractor, and a witness who had been frightened into silence.
And someone had just told me to ask Miles Ansar what he had seen.
I looked at the message again.
Then I noticed the timestamp.
The message had been sent at 4:19 p.m.
One minute after the last confirmed transmission from my vehicle.
I turned the phone toward Daniel.
He read the timestamp.
His face lost its color.
"That's impossible," he whispered.
"Why?"
He looked at me.
"Because the number that sent this message belongs to a device that was officially deactivated three years ago."
I stared at him.
"Whose device?"
Daniel hesitated.
Then he said a name I recognized from the sealed case file.
Owen Rusk.
May you like
And suddenly, the question was no longer who had sent the warning.
The question was why a man whose phone had supposedly been deactivated three years earlier was sending messages from it at the exact moment my federal tracking signal disappeared.