Mercer did not argue with that. Maya asked Lena to open the payment file for the technology project. The contract had been funded through city appropriations and a federal technology grant. Payments were released in stages: the first covered equipment purchases, the second covered installation and integration, and the final payment was authorized after the department certified that the project had been completed and tested.
Lena opened the last payment record. The status read: Paid in full.
Maya checked the amount: more than two million dollars had been released across the project.
“Who approved the final payment?” she asked.
Lena opened the supporting documents. “City finance processed it after the department submitted the completion package.”
“Who signed the departmental acceptance?”
“Chief Mercer.”
Mercer stepped closer. “I signed based on the technical completion documents provided to my office.”
Maya nodded. “Who provided them?”
“Sloan Integrated Systems.”
“Did anyone from the department independently verify the equipment?”
“Our IT staff worked with the contractor.”
Lena looked at him. “I wasn’t asked to verify the final installation.”
Mercer turned toward her. “You weren’t the project manager.”
“No, but I was responsible for the evidence system they said they upgraded.”
Rebecca, standing near the second workstation, interrupted: “That still doesn’t mean the Chief knew the equipment was sitting in storage.”
Maya replied, “No one has said he did.”
Rebecca appeared frustrated. “Then what exactly are you suggesting?”
“I’m not suggesting. I’m establishing who certified what.”
Maya asked the technician to create a list of every device found in storage that was simultaneously recorded as active. The list grew steadily. By the time the technician stopped, it contained dozens of serial numbers.
Maya looked at Mercer. “These aren’t paperwork errors affecting one shipment.”
Mercer studied the screen. “Then I want Calvin Sloan contacted.”
“No.”
“He was the contractor. He can explain the installation.”
“He can explain it after we preserve his records.”
Mercer’s expression tightened. “You intend to investigate the vendor without giving him an opportunity to respond?”
“I intend to prevent anyone connected to this contract from changing records before we know what exists.”
Rebecca said, “You’re talking about my brother.”
“I’m talking about the contractor.”
Maya asked Lena for the project work orders. Several listed overnight installation periods inside restricted areas of the department. Each work order showed the task as completed. Rebecca’s name appeared on the security approvals.
Maya pointed to one entry. “This says the contractor had access from late evening until early morning.”
Rebecca nodded. “That was normal. We scheduled technical work after administrative hours so the evidence office could keep functioning during the day.”
“Were you here?”
“Sometimes.”
“And when you weren’t?”
“A shift supervisor handled access.”
“Do the records identify the supervisor?”
“They should.”
Lena searched. Some did; others did not. Several overnight entries showed the contractor credential entering the building, but there was no corresponding employee name attached to the access event.
Maya asked, “Would that normally happen?”
Lena shook her head. “Someone from the department should have been assigned to the restricted area.”
Rebecca said, “The logs are incomplete. We already know that.”
“Which is why we preserve everything that remains,” Maya replied.
One of the FBI technicians called Maya over to another workstation. “I found something in the contractor certificate history.”
He displayed a list of authentication events connected to Sloan Integrated Systems. The contractor certificate had accessed the network well outside the dates listed on the maintenance schedule.
“How often?” Maya asked.
“Regularly.”
“From inside the building?”
“Not always. Some sessions appear remote.”
Mercer frowned. “Remote support was included in the contract.”
The technician nodded. “Limited remote maintenance was included. These sessions reached more than the documented maintenance environment.”
“What kind of access?”
“Evidence indexes, system configuration, retention controls, and portions of the vehicle data interface.”
Rebecca stepped forward. “Calvin’s company supported multiple city systems. That may be normal.”
The technician looked at Maya. “It might be, if there’s documentation authorizing it.”
Maya asked Lena, “Is there?”
“Not that I’ve found.”
Maya told the technician to preserve the certificate activity, but not disable the credential.
Mercer looked at her. “You’re leaving an account active that you believe may have exceeded its authority?”
“I want to see whether it connects again.”
Rebecca shook her head. “You’re waiting for someone to make a mistake.”
“I’m preserving evidence of what the account does on its own.”
The distinction ended the discussion.
Lena opened another folder containing the project’s testing reports. Each document stated that backup systems had passed verification before final acceptance. Maya noticed that the test reports shared the same digital author: Calvin Sloan.
Lena nodded.
“And who witnessed the tests?”
Lena searched the forms. The witness field was blank on several reports. On others, the entry simply read: APD authorized personnel. No individual was named.
Maya asked Mercer, “Did you personally witness the final system test?”
“No.”
“Did Rebecca?”
Mercer looked toward her.
Rebecca answered for herself: “No. My responsibility was physical security.”
Maya turned back to Lena. “Then find whoever did.”
Lena searched the project calendar, staff assignments, and IT records. After several minutes, she stopped. “I can’t find anyone.”
Maya looked at the “paid in full” authorization again. The city had released millions of dollars for equipment recorded as installed, tested, and operating. Much of that equipment remained sealed in storage. The final testing reports did not identify a departmental witness, and the contractor retained system access broader than the written agreement described.
She gave the federal team its next instructions: “Preserve every invoice, every acceptance certificate, every payment authorization, and every Sloan administrator session. Keep the police systems running, but mirror all contractor activity.”
Lena nodded.
Maya then looked at the active network diagram on the wall monitor. “Now compare this diagram with the building’s physical infrastructure.”
The technician began loading the plans. If Asheford’s official system could not account for its equipment, Maya wanted to know whether another system was operating where the record said nothing should be.
By early afternoon, the federal team had built a document chain that connected the technology project from purchase to final payment. Each record answered one question and raised another.
Maya stood beside a conference table where the files had been arranged in order: purchase authorization, delivery records, contractor work orders, security approvals, completion certifications, and payment releases.
One of the FBI agents pointed to the first document: “Equipment purchased with federal and municipal funds.” The next file showed delivery to Asheford. The third showed the equipment transferred for installation. The fourth certified the work as complete. The fifth released final payment.
Maya looked at the signatures: Calvin Sloan had certified the technical work; Chief Daniel Mercer had accepted the completed project on behalf of the department; Rebecca Sloan had approved restricted area access during multiple installation periods.
Rebecca stood across the table. “We’ve already covered my signature. It certifies access. It does not certify installation.”






