Evelyn asked whether the $18.4 million was now at risk. Thomas explained that the hold did not automatically cancel the partnership or withdraw allocated funding. Certain implementation actions would pause while the original data was authenticated, and the county would have an opportunity to maintain the program under appropriate oversight. Hearing that distinction allowed her to concentrate on the evidence rather than on the immediate fear of losing a public-safety investment.
Martin turned a page. "It says a preserved project state is created automatically. Did that happen?"
"Yes," Thomas said. "The archive is independent of the routine sheriff's office system. Existing version histories were copied and protected. Subsequent changes are recorded against the preserved cutoff."
Cole leaned forward. "Independent from whom?"
"From any single county official who might be involved in the dispute."
"So federal contractors are duplicating county records because I dismissed one employee."
"The county agreed to an independent preservation system because the integrity of the project cannot depend on a disputed official controlling the only copy of the evidence," Thomas answered.
Evelyn looked at Cole. "Did you review this provision before you terminated her?"
"I reviewed the parts relevant to my authority. I don't require federal permission to manage my command staff."
"No one said you did," Thomas replied. "This is a records consequence, not a request for personnel permission."
Martin returned to the internal report. "The export is attributed to Maya's username. What does the original metadata say about the source of the command?"
Cole opened his portfolio. "Her credentials were used. The original report shows that clearly."
"The source field points to the central administrative gateway," Martin said. "We need the gateway's authorization history."
Cole's expression hardened. "Are you questioning the report?"
"The state inspector is questioning the evidence, because that's the purpose of the referral," Martin answered. "An account label isn't necessarily the identity of the person operating it."
"You think my office altered it?"
Thomas kept his voice even. "I haven't accused your office of altering anything. I'm asking for server-side metadata rather than a report assembled from selected fields. The former tells us what the system recorded. The latter tells us what someone chose to include."
The room went quiet. Evelyn closed her notebook and decided that the county's interest was better served by giving the inspector the original data than by debating why a request for it might feel insulting. She instructed Martin to coordinate direct preservation and delivery with county technical services. Cole said little after that, though he made certain to repeat that his department would cooperate fully.
When he returned to the sheriff's office, he found Owen standing beside an IT administrator whose laptop displayed the Safe Communities access controls. Cole stopped in the doorway. The administrator straightened. Owen remained seated.
"What is this?" Cole asked.
"The raw metadata export county counsel requested," the administrator said. "The system has also marked the project record as write-protected under Appendix K."
"I know about the hold."
"It's more than a notice. The archived version was mirrored when Captain Williams's personnel status changed. We can't alter that preserved copy from this network."
Owen asked whether the same protection applied to administrators. The woman explained that any later update would create a new version with its own timing and authorization trail. Cole looked from her to Owen, then back at the screen.