Then Jordan asked how his mother and grandfather could remain so calm while television stations argued about whether she should ever work in law enforcement again. Maya admitted that she was angry, frightened, and more tired than she wanted to say. She told him that giving those feelings to a camera would not improve the evidence. Isaiah added that the kind of anger people could use against her was often the kind that felt most satisfying for five minutes.
"You two make everything sound like testimony," Jordan complained.
"Sometimes that's because everything you say might become somebody else's version of events," Isaiah replied.
Jordan looked at his mother. "Do you think Cole framed you?"
"I think there are records that don't match the system history. I think somebody had access to the administrative gateway that I didn't have. I think an acknowledgement appeared after my account was disabled. I'm not going to turn those facts into an accusation against a particular person before the evidence does."
"It sounds like you're protecting him."
"I'm protecting the conclusion from being weaker than the facts," Maya answered.
At Dawson's, Cole checked his phone and saw no new public statement from Maya. He took her silence as a sign that the latest document had left her without an answer. Across town, the state inspector's analysts were opening two versions of the Safe Communities packet side by side. One was the last preserved version recorded before Maya lost access. The other was the packet Cole had included in the referral.
The discrepancy appeared on a page marked Protected Classification Notice. It existed in the referral, but there was no equivalent page in the preserved earlier version. The analyst checked the metadata, compared the timestamps, and confirmed that the additional notice had been created after Maya's county credentials were disabled. Its presence made the records described in the referral appear subject to a stricter classification warning than the one evident in the earlier packet.
The analysts documented the finding without claiming that every later amendment was improper. A compliance packet could legitimately be updated, but changes should have a reason, an authorization history, and an accurate representation of when they became effective. Here, the new page was being used to support an allegation about actions that predated its creation. The difference was consequential enough to demand an explanation.
The next morning, Evelyn and Martin reviewed the two versions. Evelyn placed her finger beside the new page and asked whether Cole had been notified. Martin confirmed that the sheriff had received the preliminary comparison. She requested another meeting before a public statement could transform a disputed classification into an accepted fact.
Cole arrived with his folder and sat without being invited. Martin laid out the version comparison and explained the timing. Cole responded that administrative processing often continued after an employee left, which was true. Then Martin placed an approval record beside it showing that the change had passed through privileges associated with Cole's command certificate.
"I approve hundreds of routine requests," Cole said. "That doesn't mean I personally typed every line."
"No one has claimed that an approval alone establishes who sat at the terminal," Martin replied. "But your authorization appears in the path. We need to know what was requested and why it changed the material being used against Captain Williams."
"Ask IT."