He denied instructing anyone to provoke a confrontation. He denied knowing that Ryan would handcuff Danielle. He denied directing anyone to intimidate Patricia or locate Thomas.
Some of his answers were plausible.
Others were evasive.
The hearing could not resolve which.
When Pierce finished, the chair announced that the investigation would continue and that the council would consider temporary restrictions on access to sensitive dispatch systems.
Pierce returned to his seat.
As he passed Danielle, he stopped.
“I hope you're satisfied,” he said quietly.
She looked at him.
“No.”
His expression sharpened.
“You've suspended officers, disrupted a contract, and turned the department into a public spectacle.”
“I didn't change the records.”
“You don't know who did.”
“Correct.”
“Then perhaps you should stop treating everyone as guilty.”
Danielle held his gaze.
“I haven't. I've asked for evidence. You've been given the opportunity to provide yours.”
Pierce lowered his voice.
“Be careful, Mayor. Sometimes the people who claim to be protecting the truth end up destroying everything around them.”
Danielle's expression did not change.
“Then we should make sure the truth is strong enough to survive being examined.”
She walked away.
Pierce remained standing for a moment before returning to his seat.
His threat had been subtle.
But it was a threat all the same.
And Danielle had no intention of allowing it to influence the investigation.
Chapter 18: The Evidence That Changed Everything
Two days after the hearing, Dr. Price made a discovery that transformed the investigation.
The independent team had recovered a backup of the communications system stored on an isolated server. The backup had not been part of the ordinary dispatch archive, and its contents had not been included in the first export supplied by the department.
The server contained an older version of the routing configuration.
It also contained a message thread that appeared to have been removed from the current system.
Evelyn called Danielle and Marcus into the forensic laboratory.
“We found a message from the evening before the arrest,” she explained.
“Who sent it?” Danielle asked.
“The account belongs to the CivicShield project administrator. The recipient was an administrative account within the police department.”
“Can we identify the individual user?”
“We have a workstation log that may help. But first, look at the content.”
She displayed the message.
The appointment must not proceed as scheduled. If the visitor is delayed, the review will be postponed. Use the existing response procedure. No direct contact with the mayor.
Marcus frowned.
“This is more explicit than the other message.”
“Yes,” Evelyn said. “It establishes that someone wanted the appointment delayed. It doesn't, by itself, establish that the sender intended an arrest.”
Danielle read it again.
“Was there a response?”
“Yes.”
A second message appeared.
Understood. We will route the report through standard operations. The responding unit will receive the summary.
The message was signed with an internal account reference.
Evelyn displayed the account history.
“The account was active on a workstation assigned to the deputy chief's administrative suite.”
“Who used the workstation that evening?” Marcus asked.
“We have not established that conclusively. The access records show that the workstation was unlocked using a valid credential. The building's access logs show three people entered the suite during the relevant period.”
“Names?”
“Deputy Chief Pierce, an administrative assistant, and a technical contractor.”
Danielle remained still.
“Can we establish whether the messages were part of the same thread as the instruction to withhold the appointment details?”
“Yes. The message identifiers match.”
“So the same operation involved delaying the meeting, routing a report, and withholding context from the responding officer.”
“That is what the records suggest.”
Marcus leaned forward.
“Why would they need to delay the meeting?”
Evelyn opened another document.
“The calendar invitation included a reference to the communications contract review. A later revision removed that reference.”
Danielle looked at the screen.
“Who made the revision?”
“The calendar system shows that the change originated from an account in the executive administration office.”
Marcus exhaled.
“Philip Warren's office.”
“Possibly someone working under his authority,” Evelyn replied. “The account is assigned to a scheduling coordinator. We have not yet established who requested the change.”
Danielle's expression tightened.
The investigation had reached a point where nearly every major office appeared in the records.
Police administration.
Contract management.
The mayor's executive office.
CivicShield.
The temptation to connect the dots into one sweeping accusation was strong.
But the evidence still had gaps.
She looked at Evelyn.
“What do we know with confidence?”
Evelyn considered the question.
“We know that the appointment was known to people beyond the three individuals you originally identified. We know that someone attempted to access your calendar. We know that a message instructed an administrator to delay the appointment. We know that a report was routed to Officer Mitchell with limited context. We know that the report's language described the subject as likely to become confrontational before the officer had spoken to you.”
“And what don't we know?”
“We don't yet know who originated the plan, who physically sent the messages, or whether every person whose account appears in the records understood the intended outcome.”
Danielle nodded.
“Then those are the questions we pursue.”
Marcus pointed to the first message.
“There is another possibility. Someone may have wanted to delay the meeting because the contract review threatened their financial interests. The confrontation may have been intended to discredit you or simply prevent the meeting from happening.”
“Either possibility is serious,” Danielle said. “But we need evidence of intent before making a public claim.”
Evelyn enlarged the final line of the message.
No direct contact with the mayor.
Danielle stared at it.
That instruction bothered her more than the others.
Whoever had written it had anticipated that she might be contacted directly. They wanted the response to happen without a conversation that could clarify the circumstances.
They had wanted distance between the people arranging the response and the person who would experience it.
The plan depended on intermediaries.
A message passed to an administrator.
A summary passed to dispatch.
A dispatch entry passed to an officer.
Each person could claim to have followed routine procedure.
Each person could insist that the decision belonged to someone else.
And the person at the center of the incident could be left trying to prove that the sequence had been designed.
Danielle closed the folder.
“Secure the original backup. Make two verified forensic copies. Document the process. Then provide the material to the investigator and the appropriate legal authorities.”
Evelyn nodded.
“We'll do that.”
Marcus looked toward Danielle.
“If this becomes public before the investigators are ready, the city will be overwhelmed.”
“Then we should prepare to explain the facts clearly. But we won't conceal evidence simply because it is politically inconvenient.”
She stood.
“Someone thought they could prevent a meeting by manipulating an ordinary procedure. We are going to find out who, and we are going to make sure the system cannot be used that way again.”
Chapter 19: Thomas's Full Statement
Thomas Ellison met with Investigator Foster the following morning.
His attorney was present, along with an independent advocate who had helped arrange his protection. The interview was conducted in a secure office outside police headquarters.
Thomas had spent the previous night reviewing his records and preparing a timeline.
Foster began by asking him to explain his role at CivicShield.
“I was a systems analyst,” Thomas said. “I worked on configuration, testing, and access controls. I didn't make policy decisions.”
“What did you discover?”
“I noticed that certain dispatch records were being changed after they were submitted. Sometimes the changes were ordinary corrections. Other times, they altered how the original report described the person involved.”
“Can you give an example?”
Thomas opened his notebook.
“One report said a resident had asked whether a building entrance was open to the public. The revised summary said the resident had refused to follow access instructions.”
“Did the original report support that conclusion?”
“No.”
“Did you raise the issue?”
“Yes. I submitted a technical complaint.”
“What happened?”
“My supervisor told me the changes were authorized by the department. I asked for the approval record. He told me to stop questioning operational decisions.”
“Who was your supervisor?”
“Martin Vale.”
“Did he explain who had authorized the changes?”
“No. He said the department had requested flexibility.”
“Did you believe that explanation?”
“Not after I examined the logs.”
Thomas described how he began comparing the original reports with the revised versions.
He found cases where uncertain language had been replaced with definitive statements. He found records where the person involved had requested clarification, but the summary described the request as resistance. He found entries where the responding officer had been given less information than the original caller provided.
Foster listened carefully.
“Did you find evidence that officers were instructed to make arrests?”
“Not in a direct written instruction. The records showed changes that could influence their decisions, but I can't say what every officer was told or intended.”
“Did you find evidence that the system was used to target particular people?”