The Officer Believed He Had Trapped an Ordinary Black Driver. Four Minutes Later, the President's Motorcade Was Speeding Straight Toward Him.

Chapter 23

Theme:
Font Size:
24px

Daniel nodded slowly.

"I suppose that's what makes this so difficult. I wanted to believe the system would work when I needed it."

He pushed open the door.

Outside, the air was cool and bright.

"And when it didn't," he continued, "I started thinking maybe I was the problem."

Rachel stopped walking.

"You were not the problem."

"I know that now. Mostly."

She squeezed his arm.

"Then keep remembering it."

They continued toward the parking lot.

For Daniel, the investigation was not about winning an argument or watching Mercer suffer. It was about recovering something he had lost when the handcuffs closed around his wrists: the confidence that he could move through ordinary life without constantly wondering whether someone else's assumptions would destroy it.

He knew the process might take months.

He knew the findings might be incomplete.

But he had finally stopped treating his own experience as something he needed to apologize for.

And that was a change no administrative decision could take away.

The next significant discovery came from the department's digital evidence archive.

A technical analyst named Priya Nair had been examining access logs associated with the camera recordings. She was not a police officer and had no authority to determine whether anyone had committed misconduct. Her task was to establish when recordings were created, accessed, copied, or modified.

The work was tedious.

Thousands of entries appeared in the system, many associated with routine patrols, training exercises, and equipment checks. Most showed nothing unusual.

But when Nair compared the logs with the complaint records, she noticed that several files had been accessed by an administrative account shortly before the related complaints were closed.

The account belonged to a shared workstation in the professional standards office.

Shared accounts were not unusual in older systems, but they made it difficult to establish which employee had performed a particular action.

Nair checked the system configuration.

The workstation had a secondary audit function that recorded certain operations separately from the main user log. The function had been enabled during a software update but was rarely used because the department had never incorporated it into routine reviews.

She exported the available data and sent it to Shaw.

The new records showed that someone had opened the Price recording on the morning the complaint was closed.

That fact contradicted the assumption that the footage had never been reviewed.

However, the logs did not identify the person who had watched it, and they did not establish whether the recording had been viewed in full.

Shaw brought the information to Bennett.

"We have confirmation that the file was opened," she explained. "We don't yet know who opened it or what they saw."

"Can we connect the session to a specific workstation user?"

"Not from this log alone. The workstation was using a shared account."

"Are there any other records?"

"The secondary audit log shows the session began at 8:42 a.m. and ended at 8:49 a.m. The closure letter was generated at 9:03."

Bennett studied the times.

"Twenty-one minutes between the beginning of the session and the closure letter."

"Correct."

"Was the file long enough to watch in that period?"

"Yes, but the recording included several minutes of inactivity and the interruption. We cannot establish whether the person watched all of it."

"Then don't claim they did."

"I won't."

Bennett looked at the report again.

"Find out who was assigned to that workstation that morning. Check the duty roster, access records, and any maintenance logs."

Nair joined the conversation through a secure video call.

"I've already started," she said. "There is one complication. The workstation's login history was partially overwritten during a routine maintenance cycle. We may be able to recover fragments from the backup server, but it won't be straightforward."

"Proceed carefully," Bennett said. "Make forensic copies before attempting recovery."

"Understood."

The team worked through the afternoon.

By evening, Nair had recovered part of the backup log. It showed that Lieutenant Haines had logged into the workstation shortly before the recording was opened.

That did not prove that he had watched the footage himself. Someone else could have used the workstation while it remained logged in, and the audit system was not designed to establish individual identity with certainty.

But it created a direct connection between Haines and the file at a critical moment.

Shaw requested another interview.

Haines's representative asked for time to review the new material.

The interview was scheduled for the following week.

Meanwhile, Bennett informed Chief Whitaker that the investigation had identified a new evidentiary issue.

Whitaker listened carefully.

"Do you believe Haines deliberately concealed the recording?"

"I don't know."

"Do you believe Reeves knew?"

"I don't know that either."

News in the same category

The Officer Believed He Had Trapped an Ordinary Black Driver. Four Minutes Later, the President's Motorcade Was Speeding Straight Toward Him.

45 Part