Jordan called his lawyer and described the conversation in detail. Marcus listened without interrupting.
When Jordan finished, Marcus asked him to read the name of the security firm printed beneath Adrian's contact information.
“Northbridge Risk Advisory,” Jordan said.
Marcus paused.
“I know the name.”
“You do?”
“I've seen it mentioned in connection with a few municipal technology contracts. I don't know anything about this individual, but we should verify his identity before responding.”
“Do you think he's telling the truth?”
“I think we have no reason to accept his claims without evidence. I also think we should not ignore information that might be relevant. Keep the card. Photograph it. Write down the exact words he used.”
Jordan looked at the notebook on the table.
“I already started writing everything down.”
“Good. Add this conversation. Do not contact him until we have checked his background.”
After the call, Jordan searched his email for the old application. It took several minutes to find it. The rejection message was still there, dated fourteen months earlier.
He opened the original technical assessment he had saved as a PDF.
At the time, he had considered the exercise an ordinary hiring test. It described a fictional city using a data platform to prioritize neighborhood complaints. The system assigned risk scores based on reports of unusual activity, repeated calls to the same address, and patterns of movement detected by public cameras.
Jordan had noticed that the model treated repeated complaints as independent evidence, even when they originated from the same person. A single resident could submit multiple reports about the same individual, and the system might interpret those reports as confirmation of a pattern rather than as repetition by one source.
He had written a lengthy explanation of the problem and proposed safeguards to prevent a single person's bias from distorting a risk score.
He had never heard back about his analysis.
Now he read his own words again.
The flaw was obvious once he saw it.
A system designed to detect risk could mistake repetition for corroboration. A false or biased report, repeated often enough, could acquire the appearance of truth.
Jordan leaned back.
He did not know whether Meridian's system had anything to do with the incident. He did not know whether Adrian was a whistleblower, a consultant, or a man trying to manipulate him.
But the possibility that someone could use technology to turn an unsupported suspicion into an official record frightened him more than the arrest itself.
The arrest had been visible.
The system Adrian described could operate quietly, long before anyone saw a patrol car.
The next morning, Marcus arrived at the Ellis house carrying a legal pad and a laptop.
Jordan showed him the email, the assessment, and the business card.
Marcus read the assessment carefully.
“This is more detailed than I expected,” he said.
“I was trying to get the job.”
“You identified a genuine methodological problem. Repeated reports from one source should not automatically be treated as independent confirmation.”
“Could a system like this really influence police activity?”
“Technology can influence what information reaches an officer. Whether it influenced your case is a separate question. We need documents, not assumptions.”
He examined the rejection email.
“Did Meridian provide any feedback on your assessment?”
“No.”
“Did you sign a confidentiality agreement?”
“Not that I remember.”
“Did they retain the materials you submitted?”
“Probably. The application portal said they might keep candidate information for future openings.”
Marcus made a note.
“Let's preserve everything you have. Emails, attachments, dates, names, and any messages about the assessment. Don't edit the original files.”
Jordan opened the PDF again.
“What if this really is connected?”
“Then we follow the evidence wherever it leads. But we cannot allow a theory to become another unsupported accusation.”
Jordan smiled faintly.
“You sound like Chief Carter.”
“I'll take that as a compliment.”
Marcus closed the laptop.
“One more thing. If someone is attempting to pressure you, the worst thing you can do is react publicly before we understand the situation. Stay calm. Keep records. Let the facts accumulate.”
Jordan looked at the basketball resting near the back door.
“I was just playing a game.”
“I know.”
“That was all I was doing.”
Marcus followed his gaze.
“Sometimes the most important fact is the simplest one. But we still have to establish what happened around it.”
At the police station, Chief Carter received a preliminary report from the department's digital evidence team. The audio enhancement had clarified a few sounds from the recording near the corner, though the words remained incomplete.
The technician had isolated a short exchange between Miller and the unidentified man.
A voice could be heard saying something that sounded like, “That's him.”
The recording then captured Miller responding with a brief question, but the words were too distorted to interpret confidently.
Carter listened to the clip twice.
He did not like how little it revealed.
He liked even less how easily a fragment could be used to construct a story.
“Could the voice belong to Officer Miller?” he asked the technician.
“Possibly, but I can't identify the speaker reliably from this sample.”
“Could the phrase be something else?”