Andrew looked down at the report.
"There isn't a separate review process for every restriction."
Jonathan turned to Martin.
"Do you see the problem?"
Martin replied, "The system is designed for efficiency. Employees must make quick decisions during busy periods."
"Efficiency is not the same as accountability."
"We can't investigate every passenger complaint."
"No one has asked you to. We are talking about patterns that suggest the process may be deliberately manipulated."
Jonathan pointed to a row of transactions.
"Look at these. Each restriction was applied by a different employee, but the same authorization code was used to remove it. The fees were collected through separate transactions, yet the final adjustment was recorded under a single administrative account."
Priya leaned over the table.
"That's unusual."
"Could one account legitimately process all those adjustments?" Jonathan asked.
"Yes, if it belongs to a centralized supervisor. But the authorization history should identify the person who approved each transaction."
"Does it?"
Priya checked the details.
"No. The approval field is blank."
Jonathan felt a familiar sense of unease. A missing record did not automatically indicate wrongdoing, but repeated omissions across unrelated systems suggested a structural weakness.
"Find out whether these transactions connect to the Gate 41 account," he said.
Before Priya could respond, a security officer appeared in the doorway.
"Mr. Reed, there's someone asking to speak with you."
"Who?"
"She says her name is Evelyn Brooks. She works for Northbridge Technical Services."
Martin immediately stood.
"Tell her to submit a formal report through the contractor office."
The officer hesitated.
"She says it's urgent. She also says she has evidence concerning the access breach."
Jonathan looked at Martin.
"Bring her in."
A minute later, a woman in her early forties entered the room. She wore a plain gray cardigan over a white blouse, and her hands trembled slightly as she held a sealed envelope. Her visitor badge was clipped backward, as though she had attached it in a hurry.
She looked first at Jonathan, then at Martin.
When she saw the chief security officer, she stopped.
"I was told you would be alone," she said.
"You can speak freely," Jonathan replied.
Evelyn shook her head.
"Not with him here."
Martin's expression hardened.
"This is a restricted operations room. You don't get to decide who stays."
Evelyn looked at Jonathan again.
"Please. I know what happened to the missing module. I know why your credentials were used. And I know who has been changing the passenger records."
The room fell silent.
Jonathan gestured toward an empty chair.
"Sit down, Ms. Brooks."
She remained standing.
"If I tell you what I know, I need protection. My employer has already suspended me, and someone followed me to the airport this morning."
Martin scoffed.
"That's a serious accusation."
"I know."
"Do you have proof?"
Evelyn tightened her grip on the envelope.
"Yes."
Jonathan studied her face. She looked frightened, but not confused. Her fear seemed to come from knowing precisely how much trouble she could be in.
He turned to Andrew.
"Arrange for an independent security officer to accompany Ms. Brooks. No one from her contractor team. No one from Mr. Hale's direct staff."
Martin stepped forward.
"That is unnecessary."
"Then you should have no objection to an independent review."
Jonathan looked back at Evelyn.
"You will not be asked to hand over your evidence without a record of what you provide. Your statement will be documented, and you will be given a copy. But I need you to understand something: I cannot promise that every claim you make will prove true. We will verify it."
Evelyn finally sat.
"That's all I want."
She opened the envelope and removed several printed pages. The first showed a maintenance work order for Gate 41. The second contained a list of equipment serial numbers. The third was a screenshot of an internal messaging application.
Jonathan read the first page.
A contractor had been authorized to install a temporary network monitoring device during a scheduled maintenance window. The authorization had been approved by an account belonging to the airport's security administration.
"Who requested this work?" Jonathan asked.
Evelyn pointed to a name in the approval field.
"Martin Hale."
Every eye in the room turned toward the chief security officer.
Martin did not flinch.
"I authorize dozens of maintenance operations every month. That document proves nothing."
"You're right," Jonathan said. "It proves that an authorization was issued under your account. It doesn't establish who physically approved it or why."
He turned back to Evelyn.
"What happened to the device?"
"The installation team was told to remove it after testing. But when we arrived the next morning, the device was gone. The work order had already been closed."
"Did you report the missing equipment?"
"Yes. I submitted a discrepancy report."
"To whom?"
"Mr. Hale's office."
Martin's expression remained controlled.
"And what response did you receive?" Jonathan asked.
Evelyn slid another sheet across the table.
The report had been marked DUPLICATE ENTRY — NO ACTION REQUIRED.
Jonathan examined the timestamp. The report had been closed less than four minutes after submission.
"Who closed it?"
"The account belonged to the security administration."
Martin leaned forward.
"Anyone with the correct permissions could have used that account."
"Exactly," Evelyn replied. "That's why I started keeping copies."
She reached into her bag and produced a small encrypted storage device.
"This contains the original work order exports, the maintenance messages, and the system logs I was able to save before my access was revoked."
Priya examined the device without connecting it to the airport network.
"These files need to be handled in an isolated environment."
"Agreed," Jonathan said.
He looked at Evelyn.