The earlier request had been submitted several months before, shortly after the record was transferred to the regional system. It asked whether the identity entry could be closed or corrected. The response stated that no action could be taken without additional documentation. The request had been marked pending and had never been formally resolved.
Marcus checked the date again. The earlier request predated the recent access events, the financial verification email, and the traffic stop. It suggested that someone had noticed a problem with the record months before Emily knew anything about it.
FPI Agent Marcus Bell: "Director, there was an earlier attempt to review or correct the entry. It was left pending."
Director Thomas Vale: "Who submitted it?"
FPI Agent Marcus Bell: "The name is masked in the summary. The archive may have the original request."
Director Thomas Vale: "Add it to the access request. We need the request itself, the response, and the reason it was left unresolved."
Marcus added the reference to the case log. The new detail changed the timeline once again. The record had not simply remained untouched in an old database. Someone had attempted to review or correct it, but the process had stopped without a documented conclusion.
That did not prove that the record was false. It did not establish that the person who submitted the review request had any connection to the officer. But it meant that the question of accuracy had been raised before the roadside confrontation, and the answer had never been properly documented in the material currently available to the investigators.
At home, Emily was still awake when her phone vibrated again. She looked at the screen, expecting another message from the unknown number. Instead, she saw a notification from the financial services company. The message confirmed that her earlier verification concern had been escalated to a security review team. It asked her to contact the company through its official support channel and warned her not to share account credentials with anyone who contacted her unexpectedly.
Emily read it twice. The company had not confirmed fraud, and the message did not mention FPI or the traffic stop. It might have been an ordinary follow-up to the earlier verification issue. Yet the timing made her uneasy.
She saved the notification and sent the reference to the official FPI contact address Elena had provided. She included a short note explaining that the message had arrived that evening and that she did not know whether it was connected to the investigation.
Then she placed the phone on the table and looked at the notes she had written. Her account of the roadside incident filled several pages. The record of the unfamiliar call, the financial verification email, and the unknown message now formed a separate timeline beside it.
She did not know what the information meant. She did not know whether the officer had seen her record, whether someone had deliberately directed him toward her, or whether the FPI response had been triggered by an automated process that nobody fully understood. She knew only that the questions were real and that she had a right to ask them.
The following morning, Elena received Emily's update and added the new notification to the investigative file. She then requested a meeting with the financial services company's security team through the appropriate channel. The request asked only for confirmation of the verification event and any available metadata relevant to the date, source, and type of request. It did not seek unrelated account details.
Marcus, meanwhile, received a partial response from the historical personnel directory. The archived account that had approved the original transfer was linked to a position within the former administrative program. The employee's name was still unavailable, but the position had belonged to a unit responsible for reviewing identity-verification cases that could not be resolved through ordinary procedures.
The unit had been reorganized, and its records had been distributed across several repositories. The transfer had been part of a larger migration project. Some entries had been closed automatically, while others had remained active because their status fields were incomplete.
Emily's record belonged to the second category.
Marcus read the finding aloud to Vale and Elena.
FPI Agent Marcus Bell: "The original transfer appears to have occurred during a migration project. Emily's entry was not automatically closed because the status field was incomplete."
Agent Elena Cross: "Does that explain the restricted designation?"
FPI Agent Marcus Bell: "Not by itself. The migration process explains how the record could have remained in the regional system, but it doesn't explain the later access or the attempted modification."
Director Thomas Vale: "And it doesn't explain why the entry was accessed shortly before the stop."
FPI Agent Marcus Bell: "Correct."
For a moment, the explanation seemed almost reassuring. A migration error could account for an old record surviving in a system after its original purpose had disappeared. It could explain why the status was incomplete and why the supporting documents were difficult to retrieve. But it could not explain every detail of the timeline.
Elena looked at the historical transfer report.
Agent Elena Cross: "We need to know what the original case was about. Without that, we can't determine whether the record should have been closed."
Director Thomas Vale: "Agreed. Keep pressing for the source file and the original review request."