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

Chapter 33

Theme:
Font Size:
24px

“We haven't modified the archive,” he said. “We isolated the relevant storage volume and made a forensic copy before doing any analysis.”

“Who authorized the original decommissioning?” Bennett asked.

“The request came through operations. I can provide the ticket number and the approval chain.”

“Was the archive scheduled for deletion?”

“The server was scheduled to be retired. The data retention status wasn't clearly documented in the ticket.”

“Was anyone aware that it contained logs relevant to an open complaint?”

Feld hesitated.

“I don't know.”

Evelyn made a note.

“Please don't guess. We need the names of the people who handled the system and the dates on which they accessed it.”

Feld nodded and opened the archived records.

The first pages showed routine administrative events. System updates, authentication requests, maintenance checks, and automated processes appeared in long columns of timestamps. The relevant entries were buried among thousands of lines.

Bennett leaned toward the screen.

“Can you filter for the recording associated with Daniel Price's arrest?”

Feld entered the incident identifier.

A smaller list appeared.

There were several entries on the day of the arrest, followed by additional access events over the next two weeks. One entry showed the footage being opened from a workstation in the lieutenant's office. Another recorded an export request that had been canceled before completion.

Evelyn leaned closer.

“Can you tell us what the export request means?”

“It means someone initiated a process to copy the recording to another location,” Feld said. “The system recorded that the request was canceled. I can't determine from this entry alone whether any data was actually transferred before cancellation.”

“Is there a record of the destination?”

“The field is blank in this archive.”

“Why?”

“It may not have been captured by that version of the software. Or the information may exist in another log.”

“Can you determine who initiated the request?”

“The account is listed, but not the person. The account was associated with the lieutenant's office.”

Bennett's expression remained controlled, but Evelyn could see the tension in his jaw.

“Could the request have been a routine action?”

“Yes. There are legitimate reasons to export footage, including evidence review, training, and preparation for a formal investigation.”

“Would a canceled request normally be documented?”

“The system should retain the event. The fact that it was canceled is part of the record.”

“Can someone cancel an export after a portion of the file has already been copied?”

Feld considered the question.

“That depends on the software version and the export method. We would need to test it against a preserved copy of the system or obtain technical documentation from the vendor.”

Evelyn looked at Bennett.

“Let's do both.”

The technician continued searching.

A second entry appeared, dated the day after Price's arrest. It showed that the recording had been opened by an account associated with Mercer’s patrol unit.

“That was me,” Mercer later confirmed when the investigators called him back. “I watched the footage the afternoon after the arrest.”

The next entry was more difficult to interpret. It showed a permissions change affecting a group of users who had access to the footage repository. The change had been made several days after Price's complaint was filed.

“Does that affect whether the video could be viewed?” Evelyn asked Feld.

“It affects which accounts are authorized to access certain categories of recordings. But the change applied to multiple incidents, not just this one.”

“Was it a routine update?”

“I can't tell from the technical record alone. The change request should contain a reason.”

Feld searched the ticket system.

The request existed, but the justification field contained only a generic phrase: access alignment following operational review.

Bennett read it aloud.

“That's not an explanation.”

“No,” Feld agreed. “It's a description of the category.”

“Who submitted it?”

“The request came from the office of Deputy Chief Reeves.”

Evelyn sat back.

The name changed the scope of the inquiry.

Until that moment, the investigation had centered on the arrest, the report, and the handling of the recording by personnel who were directly involved. The permissions change suggested that a senior administrative office had become connected to the technical record after the complaint was filed.

It did not establish wrongdoing. Reeves might have approved a legitimate system update. The request might have covered dozens of unrelated matters. Yet the timing demanded explanation.

“Preserve the entire ticket history,” Evelyn said. “Every revision, every comment, every attached document. We also need the permissions configuration before and after the change.”

Feld nodded.

“Do you want us to suspend the decommissioning process?”

“Immediately.”

“It may delay the retirement schedule.”

“Then it will be delayed.”

When they left the technology division, Bennett walked beside Evelyn without speaking.

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