The first concrete development after Simon Bell's interview came on Monday morning, when Detective Raines informed Evelyn that the police had located Adrian Cole through a former business associate. Cole had not been arrested, and the investigators had made no public accusation against him. He had agreed to communicate through his representative, who requested a written outline of the matters under investigation before arranging an interview. The request was reasonable, Detective Raines explained, but it also meant the investigation would have to proceed carefully. Cole needed an opportunity to answer specific questions, and the police needed to preserve the distinction between evidence that connected him to the restricted archive and evidence that established what he had actually done.
Evelyn called me shortly after receiving the update. I was sitting at the kitchen table with the Northbridge chronology open beside my notebook, trying to understand how the original authorization could have moved from a courier delivery into a restricted archive and then disappeared from the substantive review record. Daniel was upstairs attending an online lecture, and the house was unusually quiet. When Evelyn mentioned Cole's representative, I put down my pen and listened.
"The investigators have prepared a preliminary list of questions," she said. "They want to know who issued the hold instruction, whether Cole personally handled the original authorization, and whether he knows why the comparison task was closed without a result."
"Will he have to answer all of them?"
"He can respond through the interview process, but we cannot assume what he will say. His representative may challenge the premise of some questions, and the investigators will need to verify any explanation he provides."
I asked whether Cole had been told about Simon Bell's recollection. Evelyn said the police had not disclosed the full interview statement. They intended to ask Cole about the archive procedure and his own actions before introducing witness accounts that might influence his response. If he independently described the same conversation Bell remembered, that could help establish a connection. If his account differed, the investigators would compare the discrepancy with the documents and determine what further evidence was required.
After we ended the call, I reread the assignment-sheet notation. Hold pending source confirmation. Do not release original to ordinary intake. The wording seemed less mysterious now that we knew the instruction had existed within Meridian's records. Yet it still contained no name, no explanation, and no deadline. A temporary restriction could be justified if a document's authenticity was uncertain. It became a different matter if the restriction continued without review while the system recorded the task as resolved.
Daniel came downstairs during his break and found me looking at the note.
"Have they spoken to Cole?" he asked.
"They have located him. His representative is arranging an interview."
"Do they have enough evidence now?"
"Enough to ask specific questions. Not enough to establish every answer."
He pulled out the chair opposite me. "Mom, I know you're trying to be fair. But the original authorization didn't just disappear by itself. Someone decided where it would go."
"Yes," I said. "The evidence supports that the document was deliberately held. What we don't know is who made each decision or why."
Daniel looked down at the table. He had become more careful about making accusations, but the uncertainty still troubled him. The investigation had reached into a period of my life when I had been injured, financially vulnerable, and dependent on institutions I could not monitor. He wanted the people responsible to explain themselves. I wanted that too, but I knew that a conclusion built on an incomplete account could create another problem instead of solving the first.
On Tuesday afternoon, Detective Raines asked Evelyn to attend a meeting concerning the recovered authentication log. I joined them because the discussion involved the chronology of the authorization and the meaning of the recorded status changes. The digital evidence specialist had identified a more precise sequence of events around the shared workstation. The supervisor account had been used after a clerk's session, and the task's status had changed shortly afterward. However, the older system had not captured a unique identity for the person who performed the action.
The specialist explained that the system permitted certain supervisory actions to be completed within an existing authenticated session. If the workstation had been left unlocked, another authorized employee might have been able to use the session without entering separate credentials. Alternatively, Cole himself might have used the account after the clerk had finished working. The surviving log could not distinguish between those possibilities.
"Can the system tell us whether the session was locked?" I asked.
"Not reliably," the specialist replied. "The relevant version recorded some session events but did not preserve a complete history of workstation locking. We have the account activity and the task status changes, but not a definitive record of who was physically present at the keyboard."
Evelyn asked whether other records might establish the person's identity. The specialist said the duty roster narrowed the list of possible users, while the personnel records and interviews could help establish who had access to the restricted workstation. There might also be paper logs or archived messages recording the reason for the closure. The team was searching for those records, but none had yet established a direct link between Cole and the final action.
I felt the familiar frustration of reaching a technical boundary. A record could show that an account had been used without showing who used it. A task could be marked resolved without establishing that the substantive work had been performed. A message could communicate a decision without revealing who had made it. Every system had been designed to record certain events, and everything outside those design limits had become a question for human testimony.
After the meeting, Detective Raines explained that the police were preparing a formal interview request for Cole. They would ask him to describe his role in the restricted archive, his knowledge of the Northbridge file, and any instructions he had given concerning the original authorization. They would also ask whether he remembered the source-confirmation issue and whether he had seen a comparison result before the task was closed.
"Will he be shown the assignment sheet?" I asked.
"At the appropriate point. We want his account first, then we can ask him to explain the notation and any differences between his recollection and the documentary record."
That evening, I reviewed the original evidence inventory. The blue envelope recovered from the storage unit remained one of the most important unresolved items. Its connection to the Northbridge file had been established through the archive reference, but we still did not know whether it had contained the original authorization, a related document, or correspondence explaining the source-confirmation issue. The envelope's contents had to be examined in the context of the recovered records rather than treated as an answer simply because it had survived.
I called Evelyn to ask whether the envelope had been examined for any additional markings. She confirmed that the evidence team had documented its exterior and preserved its contents, but the envelope itself had not yet yielded a reliable indication of who placed it in storage. The MR-17 reference appeared in more than one administrative record, but the connection between the code and the person who arranged the storage remained under investigation.
"If Cole handled the envelope," I said, "would that establish he knew what was inside?"
"Not necessarily. Handling a file and examining its contents are different things. We need evidence showing what he actually did."
I wrote that distinction in the margin of my notebook. The investigation kept returning to the same principle: access did not prove knowledge, opportunity did not prove action, and a status entry did not prove completion. Those distinctions were frustrating, but they were also the reason the emerging evidence could be tested rather than merely believed.
On Wednesday, Cole's representative proposed an interview for the following week. The police accepted the date and sent a list of general topics, including the restricted archive's procedures, the Northbridge source-confirmation request, the assignment-sheet notation, and the administrative closure. No substantive response accompanied the scheduling confirmation. Cole had not admitted handling the original, and he had not denied it. Until the interview took place, the investigators would continue examining the records and interviewing other former employees.
Daniel reacted impatiently when I told him the interview had been delayed.
"Why does everything take another week?"
"Because the investigators are gathering the evidence properly."
"They already have the assignment sheet, the recording, and Bell's statement."
"They have evidence connecting Cole to the process. They still need to establish which actions he personally took."
Daniel rubbed his forehead. "I know. I just don't understand how someone can supervise an archive, have a file held under his department, and then claim he doesn't know what happened."
"He hasn't claimed that yet," I reminded him.
He looked embarrassed. "You're right. I shouldn't put words in his mouth."
I touched his hand. "You want an answer. That's not wrong. We just have to leave room for the answer to be established."
The next morning, a new document arrived from Meridian's former systems administrator. It was an extract from an archived task register showing the Northbridge comparison request's status at several points during its life. The register confirmed that the task had been suspended while the source of the authorization was being verified. A later entry changed the status to administratively closed. No comparison result appeared between those entries.
The extract did not reveal who made the change, but it established that the task had not simply vanished from a queue without leaving any record. Someone had changed its status, and the system had preserved that change. The missing piece was the reason.
Evelyn sent the extract to Detective Raines and asked whether the system's closure code could have been applied when a task was transferred to another department. The specialist confirmed that the code had occasionally been used for transferred work, but such transfers normally generated a destination reference. No destination reference appeared in the Northbridge record.
That omission made the closure more difficult to explain as routine administration. It still did not prove deliberate suppression, because the destination reference could have been lost during migration or recorded in another system. But the absence now had a defined significance: if the work had moved elsewhere, the surviving file did not show where.
I added the new finding to the chronology and highlighted the unresolved transfer reference. The evidence had moved us beyond a vague suspicion that the file had been mishandled. We could now identify the exact administrative event that needed explanation: the task had changed from suspended to closed, without a surviving comparison result or a documented destination for the work.
On Friday, Detective Raines called with one final update before the weekend. The investigators had recovered an older departmental instruction sheet describing the use of the administrative closure code. It required the employee closing a task to record whether the matter had been completed, transferred, duplicated, or withdrawn. The Northbridge entry did not contain any of those explanatory details.
The instruction sheet was not proof that someone had broken the rules deliberately. It was evidence that the closure record was incomplete under the procedure in force at the time.
When I hung up, I sat for a long time without moving. The records were finally speaking in a consistent language. The original had been held pending source confirmation. The task had been suspended. The task had later been closed without a surviving comparison result or a transfer reference. A supervisor account had been used, but the person behind it remained unidentified.
Cole's interview could help explain those decisions. It might also reveal that another employee had made the final change. Either way, the questions were now specific enough that a general assurance would no longer be sufficient.
I closed my notebook and placed it beside the recovered authorization. The next week would bring another interview, another account to compare with the records, and perhaps another piece of the chain.
For the first time, I was not simply asking who had hidden the truth. I was asking who had made each decision, what evidence they had relied on, and why the official record claimed the work was finished when the result was missing.
That was a narrower question than the one I had started with, but it was also one that could finally be answered.
Click here to continue reading: PART 26: Adrian Cole’s Explanation Left One Essential Question Unanswered
I Bought My Son a Laptop With Money Nobody Knew I Had Received, and By Morning My Family Had Begun Asking Questions I Couldn’t Answer
Part 25 of 35
