“Then we will not make accusations until we verify it.”
Thomas nodded, but his face remained troubled.
“You still don't understand the worst part.”
“What is it?”
He looked directly at her.
“The system was never only about dispatching officers.”
“What do you mean?”
“It was designed to let administrators influence which incidents received attention. Some reports could be elevated. Others could be buried. And the records could be made to look like ordinary operational decisions.”
Danielle felt a chill move through her.
“Who authorized that?”
“I don't know. But the configuration was deliberate.”
A vehicle's headlights swept across the distant wall.
Thomas flinched.
“Someone followed me.”
The security specialists moved closer.
Danielle kept her voice steady.
“Thomas, look at me. We're leaving together. The evidence will be transferred under documented procedures. You won't have to carry it alone.”
He nodded.
For the first time that night, he appeared close to tears.
“I thought if I found the proof, someone would finally listen.”
Danielle placed a hand gently on his shoulder.
“I am listening.”
The headlights disappeared.
But the danger had not disappeared with them.
As they prepared to leave, Thomas handed Danielle one final sheet of paper.
It contained a list of dates and a series of internal approval numbers.
At the bottom, in handwriting that was not his, someone had written:
THE MAYOR IS NOT THE FIRST TARGET. SHE IS THE FIRST ONE WHO ASKED FOR THE ORIGINAL RECORD.
Danielle folded the paper and slipped it into the evidence envelope.
For months, she had suspected that the system was being manipulated.
Now she had evidence that someone had designed it to make manipulation difficult to detect.
And she had a witness who believed that the people responsible were still inside the institutions entrusted with protecting the public.
She looked toward the river, where the city lights shimmered across the dark water.
“Tomorrow,” she said, “we begin with the records.”
Thomas nodded.
“And after that?”
Danielle's expression became resolute.
“After that, we find out who thought they could use the law to make people disappear.”
Chapter 12: A System Built to Look Innocent
The independent forensic team began examining the drive at 1:30 a.m.
Thomas remained in a secure location under the supervision of independent security personnel. He had agreed to provide a formal statement, but only after reviewing the arrangements with his attorney.
Danielle respected his decision.
She had learned enough about the case to understand that protecting a witness meant more than promising that no harm would come to him. It meant documenting every contact, limiting unnecessary disclosure, and refusing to treat his cooperation as an obligation.
At 2:15 a.m., Dr. Evelyn Price entered the conference room.
“We have an initial result.”
Danielle looked up from the reports.
“Tell me.”
“The drive contains three categories of material: system access records, internal communications, and a spreadsheet documenting selected incidents.”
“Does the spreadsheet match the twelve cases we found?”
“It includes those twelve, plus twenty-seven additional entries.”
Marcus leaned forward.
“Thirty-nine cases?”
“Thirty-nine entries that appear to involve unusual routing or administrative intervention. We haven't established that every entry represents misconduct.”
“What's the common pattern?” Danielle asked.
“Someone marks a report as sensitive, assigns a specific response unit, and limits the visibility of the original narrative to a smaller group of administrators.”
“Why would a report need restricted visibility?”
“There are legitimate reasons. Sensitive investigations, confidential informants, and threats to public safety can require access controls.”
“Were these reports connected to those categories?”
“Some were not. They concerned ordinary disputes, questions about access to buildings, and complaints about people who were described as suspicious because of their appearance or presence.”
Marcus scanned the list.
“Who decided which reports were restricted?”
“Several administrative accounts appear in the records. One account was used more frequently than the others.”
“Pierce's?”
“Yes.”
Danielle raised a hand.
“Again, the account does not prove who was at the keyboard.”
Evelyn nodded.
“Correct. We have to distinguish account activity from individual responsibility.”
“What about the messages?”
“One is particularly relevant. It was sent from an internal address associated with the contract administration system. The sender instructed a technical employee to preserve a special routing configuration before a scheduled audit.”
“Who was the recipient?”
“Thomas Ellison.”
“Did he respond?”
“Yes. He asked whether the configuration had been approved by the city.”
Evelyn brought up the exchange.
The reply was short.
Approval is handled above your level. Preserve the configuration. Do not make changes without authorization.
Marcus frowned.
“That sounds like someone trying to prevent a technical employee from correcting a problem.”
“Possibly,” Evelyn said. “But we need the full context. A system administrator may sometimes be told not to alter a configuration during an audit.”
Danielle read the message again.
“Was the configuration itself documented?”
“Yes. It allowed certain administrative users to change priority and assignment fields without requiring a second authorization.”
“Why?”
“The original justification was operational flexibility.”
“And the security review?”
“Flagged it as a control weakness.”
“Was the weakness corrected?”
“No. The contractor recommended a later upgrade, but the change was postponed.”
“Who approved the postponement?”
Evelyn displayed the authorization record.
The approval came from a municipal technology committee.
Pierce had been listed as the police department's representative.
The committee's chair was Deputy Mayor Philip Warren.
Danielle's expression changed.
Philip Warren had served as her deputy for nearly three years. He was articulate, politically skilled, and deeply involved in budget negotiations. He had publicly supported the modernization project while privately warning that the city should avoid creating “unnecessary conflict” with established vendors.
He had also known about Danielle's meeting at the Brookfield estate.
Danielle slowly sat back.
“Could Warren have accessed the system?”
Evelyn answered carefully.
“His office had access to the committee records. We have not established that he had direct access to the police dispatch platform.”
“Then why is his name on the approval?”
“Because he chaired the committee that accepted the contractor's recommendation.”
Marcus looked at Danielle.
“This is getting closer to the executive offices.”
“Or closer to a chain of approvals that nobody properly examined,” Danielle replied. “We still need to establish which.”
Evelyn closed the document.
“There is another file. It contains an internal message sent shortly before the incident at Brookfield.”
Danielle leaned forward.
“Read it.”
Evelyn displayed the text.
The visitor will arrive at fourteen hundred. Confirm the response window. Ensure the officer receives the description, not the appointment details.
No name appeared in the visible header.
Only an internal reference number.
The room fell silent.
Marcus broke it.
“Someone deliberately withheld the appointment details.”
“Yes,” Evelyn said. “The message appears to instruct the recipient to provide a description while withholding context.”
Danielle stared at the screen.
That was the mechanism.
The officer had been told what she looked like, where she would be, and that the situation required attention.
He had not been told why she was there.
He had received enough information to recognize her but not enough to understand her purpose.
If he then acted on his assumptions, the resulting confrontation could be blamed on his judgment.
The person who had designed the situation could remain invisible.
“Can we trace the message to a person?” Danielle asked.
“Not yet. The sender field was removed from the exported copy. The original system may retain it.”
“Then we retrieve the original.”
Evelyn nodded.
“That's our next step.”
Danielle looked at Marcus.
“We need a formal statement from Deputy Mayor Warren about the committee approval. We also need to notify the city's legal counsel that the contract review is now part of an independent investigation.”
Marcus looked concerned.
“If Warren is involved, he may try to influence the response.”
“Then we document every communication with his office.”
“And if he refuses to cooperate?”
“Then we follow the law. No special treatment, no shortcuts.”
She turned back toward the screen.
The most disturbing feature of the scheme was not that someone might have abused the system.
It was that the system had been designed to make abuse resemble normal procedure.
Every action had an administrative explanation.
Every unexplained decision could be attributed to a technical issue.
Every person involved could claim that someone else had made the crucial choice.
But the messages suggested that the lack of context had not been accidental.
Someone had wanted an officer to respond without understanding the full situation.
And someone had wanted Danielle Brooks to be treated as a problem before she had a chance to speak.
Chapter 13: The Deputy Mayor's Explanation
Philip Warren arrived at City Hall at 8:45 a.m.
He wore a charcoal suit and a pale blue tie. His expression was composed, and he carried a leather briefcase in one hand.
When he entered Danielle's office, he offered a concerned smile.
“I heard about what happened yesterday. Are you all right?”
“I'm fine.”
“It's outrageous. The department needs to make sure something like this never happens again.”
Danielle gestured toward a chair.
“Please sit down.”