Fourteen Minutes

Chapter 36

Theme:
Font Size:
24px

Someone had attempted to make her authorization appear unnecessary.

The fourteen minutes were not merely a technical discrepancy. They were the space between an action and the fabricated permission that was supposed to justify it.

Olivia closed the document.

Then she called her legal counsel.

“Prepare an independent review of the proposed transaction,” she said. “Include every provision that could transfer operational control before final approval.”

“Is there a particular concern?”

“Yes.”

“What is it?”

Olivia looked through the window at the aircraft ramp.

“Someone is trying to use the company's future to excuse what they did in its present.”

She paused.

“And I intend to find out how far that goes.”

THE MAN WHO KNEW THE OLD CODE

By Wednesday afternoon, the evidence had become harder to dismiss.

Rachel Kim had recovered a deleted message from the scheduling system's archive. It was not a confession. It was not even an explicit instruction to falsify a document.

It was a brief exchange between Peter Lang and an administrative assistant in Adrian Voss's office.

Assistant: The old owner profile is still listed in the migration table.

Peter: Is it active?

Assistant: Not for normal approvals. It may still resolve if a legacy reference is attached.

Peter: Should I use the legacy reference?

Assistant: Mr. Voss says the transaction team has already cleared the movement.

The message ended there.

Rachel read it aloud in Olivia's office.

“That proves Peter knew the profile existed,” Thomas said. “It doesn't prove he understood what the system would do.”

“Correct,” Rachel replied. “It also doesn't prove who attached the final approval record.”

Olivia looked at the screen.

“Can we determine which user performed that step?”

“The record was generated through a service account, not a named employee account. The service account is supposed to create records only after a verified approval.”

“Who can configure it?”

“Systems administration, with additional authorization from compliance.”

“Who has access?”

Rachel displayed a list of authorized users.

One name stood out.

Martin Shaw, a systems administrator who had worked for Sterling Aviation for twenty-two years, had retained access to the legacy migration environment.

Martin was not a senior executive. He did not attend acquisition meetings. He rarely spoke in staff briefings unless someone asked him about a technical problem. His office was a narrow room beside the server maintenance area, where old equipment was stacked on shelves and the air smelled faintly of dust and warm plastic.

Olivia knew him by reputation more than by friendship.

Her father had trusted him.

That fact made the discovery uncomfortable.

“Don't contact him yet,” Olivia said. “First, confirm whether the account was used. Then establish the sequence of events.”

Rachel nodded. “I've already requested an independent forensic specialist. They'll create a read-only copy of the relevant systems.”

“Good.”

Thomas looked unsettled.

“Martin has been here since before the new terminal opened. If someone used his credentials—”

“We will establish what happened before deciding what it means.”

Olivia's answer was firm enough to end the speculation.

That evening, she drove to the hangar where her father had kept his tools.

The building was no longer used for daily maintenance. Sterling Aviation had expanded into newer facilities, but Olivia had preserved the old workshop because it held more than equipment. It held the memory of a man who had taught her that authority was a responsibility, not a privilege.

The workbench remained against the eastern wall. A faded diagram of a carburetor hung above it. Her father's toolbox sat beneath the bench, its metal corners worn smooth.

Olivia opened it.

Inside lay a collection of spanners, a dented inspection mirror, a small compass, and a notebook bound in cracked brown leather.

She had not read the notebook in years.

Its pages contained maintenance calculations, fuel-consumption notes, sketches of engine components, and short observations about people.

Her father had recorded everything in the same precise handwriting.

On a page near the middle, Olivia found a note dated almost thirty years earlier.

When a system allows someone to approve his own exception, the system is not protecting the operation. It is protecting the person who knows where the exception is hidden.

Below it, he had written:

Never confuse a trusted person with a trustworthy process. Trust the person enough to ask for evidence. Trust the process enough to let the evidence speak.

Olivia sat on the old workshop stool.

Her father had been a careful man, but he had not been suspicious of everyone. He believed people deserved the chance to do the right thing. He also believed no individual, no matter how respected, should be able to alter an important record without leaving a trace.

She closed the notebook.

The next morning, Rachel called with the forensic team's preliminary findings.

“The service account was used to generate the approval record,” she said. “The action originated from a terminal assigned to the systems administration area.”

News in the same category

Fourteen Minutes

45 Part