"Then we don't characterize it that way."
The analyst moved to the next screen.
"There's one more thing. The municipal contractor's work order appears to have been changed in the company's scheduling system shortly before he arrived at the intersection."
I sat up.
"Changed by whom?"
"The contractor's supervisor is checking the audit record. The initial information suggests the destination was modified after the original work order had been created."
"Was the change authorized?"
"We don't know yet."
Porter leaned back.
"Again, preserve the record and verify the change. Do not assume the contractor was involved in anything improper."
The analyst acknowledged the instruction.
I studied the timeline.
There were now several events requiring explanation, but the evidence still did not establish a single cause.
It was tempting to draw a line through every unusual entry and imagine a coordinated sequence.
That was how investigators could lose their objectivity.
The correct approach was slower.
Establish each event. Identify its source. Verify its timing. Determine whether a connection existed. Only then decide whether the events belonged to the same incident.
Porter appeared to be thinking along the same lines.
"Agent Cole, I want your formal statement completed before the end of the day. After that, you'll be available for any follow-up questions. We may also request your assistance in reviewing the operational timeline."
"Understood."
"And one more thing. The local department has agreed to preserve its records. We will coordinate any further requests through the designated channels. I don't want a jurisdictional argument distracting us from the actual investigation."
"Agreed."
She stood.
"Get your wrists checked, finish your report, and then take a break. You've had a difficult morning."
I nodded.
As I left the conference room, I glanced back at the display.
The timeline was still incomplete.
The route-status query remained unexplained. The dispatch notification had not been fully recovered. The contractor's work-order change had yet to be verified.
None of those gaps proved that someone had deliberately interfered with the operation.
But every one of them needed an answer.
And the answer would have to come from the evidence.
At 11:42 a.m., I had finished my preliminary statement and completed the medical documentation.
The marks on my wrists were superficial, but the clinician recorded the bruising and recommended that I avoid unnecessary strain for the remainder of the day.
I was returning to my office when Porter called.
"Agent Cole, can you come back to the operations room?"
"On my way."
When I arrived, the analyst team had assembled around a single workstation.
Porter stood beside the main display.
"We've recovered the original dispatch notification," she said.
I looked at the screen.
"What's in it?"
"The message is short. It identifies a traffic-control assignment and directs the receiving unit to verify the status of a vehicle at the designated intersection."
"Does it identify my vehicle?"
"Not in the portion we've recovered. It refers to a location and a verification task, not a specific person."
I considered that.
"So Lawson may have received a routine instruction to check the intersection."
"Possibly," Porter said. "But we still need to establish whether the message was displayed on his terminal and whether it was part of his authorized assignment."
The analyst enlarged the record.
"The message was transmitted through the municipal dispatch system. The audit log shows successful delivery to the unit's communications queue. It does not prove the officer read it."
"Correct," Porter said. "We need to distinguish system delivery from human acknowledgment."
I leaned closer to the display.
"Can we compare the timestamp with his terminal activity?"
"We're doing that now."
A second analyst brought up another panel.
"There's a terminal activity record showing that Officer Lawson's unit accessed the traffic-assignment interface shortly before the encounter. However, the available log does not establish which message entries were displayed."
"Then we need the device-level record," I said.
"That's the next step."
Porter nodded.
"Good. Continue through the authorized recovery process."
The analyst returned to the keyboard.
For several minutes, the room was quiet except for the soft tapping of keys and the hum of the ventilation system.
Then another record appeared.
The analyst stopped typing.
"Deputy Director, we've located the source of the route-status query."
Porter turned.
"Who initiated it?"
"The request originated from a municipal operations account assigned to the city's traffic coordination desk."
"Can we identify the user?"
"Not yet. The account was shared by several authorized personnel during the morning shift. We need the access audit to establish which session generated the request."
Porter looked at me.
"That makes the request less mysterious, but it doesn't resolve the issue."
"Agreed."
The analyst continued.
"The query appears to have been made to verify the status of the intersection. It was not a direct command to stop Agent Cole's vehicle."
I felt some of the tension leave my shoulders.
That was an important distinction.
The query might have been routine. The dispatch notification might have been legitimate. The system might have functioned correctly even if the information had not reached Lawson in a usable form.
But there was still the question of why he had detained me after I identified myself.
And whether the terminal's incomplete record was a technical failure or something else.
Porter turned back toward the team.
"Continue reviewing the terminal logs. We need the original data, not an assumption based on the audit summary."
She then looked at me.
"Agent Cole, I want you to prepare for a follow-up interview. The local department may request clarification about the sequence of events, and we need to make sure our account remains consistent with the preserved records."
"Understood."
I started to leave, but Porter called me back.
"One last question."
I turned.
"Yes, ma'am?"
"Do you believe Lawson knew who you were when he placed you in restraints?"
I thought carefully before answering.
"I believe I gave him enough information to initiate verification. I also believe the recording will show that I identified myself before he applied the restraints."
"That's not quite the same as knowing what he believed."
"No. It isn't."
Porter nodded.
"Good. Keep that distinction in your statement."
I left the room.
For the first time since the encounter began, the investigation was producing answers that narrowed the possibilities rather than expanding them.
The route-status query had come from a legitimate municipal operations account. The recovered message concerned a verification task, not an instruction to arrest anyone. The motorcade had completed its movement safely.