"I thought the system owner was handling it. I had other project work, and the warning had been documented. I didn't want to bypass the chain of responsibility unless there was a reason to believe the template was still being used."
Olivia nodded.
"That is understandable. But now we know the warning wasn't converted into a completed action."
"Yes."
"What would have helped?"
Maya thought about it.
"An assigned owner, a deadline, and a requirement to verify the fix. A message marked 'delivered' shouldn't be treated as a closed issue. Someone needs to confirm that the risk has actually been removed."
Olivia wrote that down.
"That's a useful recommendation."
Maya hesitated.
"There's something else I should mention."
Olivia looked up.
"Go ahead."
"Yesterday afternoon, I received a call from someone in executive operations asking whether the old template could be used for a one-time authorization if the signing service was unavailable."
Olivia felt her attention sharpen.
"Who called?"
"I didn't recognize the voice. The caller said they were checking a contingency procedure."
"What did you tell them?"
"I said the old template could display a signature image, but it could not produce a verified approval. I told them not to use it for an operational authorization."
"Did the caller identify themselves?"
"No. They said they were calling from the executive operations office."
"Did you record the call?"
"No. It came through the internal phone system, but I didn't think it was necessary. I assumed it was a general technical question."
"Do you remember the time?"
Maya checked her calendar.
"Approximately 4:20 p.m."
"Could you write down everything you remember, including the wording of the question and your answer?"
"Yes."
"Please distinguish what you remember directly from what you inferred. Don't try to make the account sound more certain than it is."
Maya nodded.
Olivia thanked her and left.
The call changed the timeline again.
Someone had asked about using the legacy template the afternoon before the aircraft was reassigned.
That did not prove that the caller was planning to create an unauthorized document. There could have been a legitimate contingency question, especially during a software migration. But Maya had explained that the template could not produce a verified approval and had explicitly advised against using it for an operational authorization.
The warning had been repeated verbally.
Someone had received it.
The next morning, the template had been used.
Olivia returned to her office and called Naomi Patel.
"I need the internal phone logs for the executive operations line yesterday afternoon, specifically around 4:20."
"Do you have a caller's name?"
"No. Maya Chen received a call from someone who identified themselves as being from executive operations. The caller asked whether the old authorization template could be used for a one-time approval if the signing service was unavailable."
Naomi was quiet.
"Did Maya say what she told the caller?"
"She says she explained that the template could not produce a verified approval and should not be used for an operational authorization."
"That's important. I'll ask information security to preserve the call-routing records. We may not have audio, but we should be able to identify the originating extension."
"Please do."
"And Olivia, I recommend that we now treat the possibility of deliberate misuse as a formal line of inquiry."
"Agreed. But we still need to distinguish the possibility from the conclusion."
"Of course."
After the call, Olivia sat in silence for a moment.
The fourteen-minute window had begun to take on a different meaning.
It was no longer merely the period in which a document had been created.
It was the final stage of a sequence that had started the previous afternoon, when someone had asked whether the old template could be used as a substitute for a verified authorization.
Maya had said no.
The next morning, a document had appeared that used the template anyway.
The caller might have been someone who had misunderstood the answer. The person who created the document might have been someone else entirely. The shared credential could have allowed several people to act without leaving a reliable individual record.
Those possibilities remained.
But the sequence was no longer consistent with a simple, unforeseeable software glitch.
Someone had asked about the workaround.
Someone had been told it was not acceptable.
Someone had used it.
Olivia opened her notebook and wrote:
The first warning was technical. The second was verbal. The third was operational. Each time, the information existed. The failure was not a lack of knowledge alone. It was a failure to make knowledge control behavior.
She underlined the final sentence.
Then she called Dr. Ortiz in San Antonio.
The research director answered with the sound of laboratory equipment in the background.
"Olivia. I was hoping to send you the second-phase results this afternoon."
"How are things going?"
"Well. The device passed the extended temperature test. We're still reviewing the repeated-access cycle, but the early results are encouraging."