in time, change the company: she did not accept the closure. She forwarded her report - the full report, with the audit trail, with the names, with the times - to the one person in the company whose job was to refuse closure: the internal audit director, Helen Park, a woman Priya had never met, whose reputation was that she read everything, twice, and never closed a matter because an email told her to. The two-line email sat in Priya's inbox, closed, official, final. And Priya's report, forwarded, traveled - like water through cracks, like a story through a building - to a desk where it would not be closed, where it would be read, and where the two lines, "reviewed" and "no additional action was needed," would become the first exhibit in a case about who gets to decide when a matter is over, and who benefits from the hurry to declare it so.

She printed the email and carried it to her manager. Daniel scanned the page without inviting her to sit.

"You need to stop reopening this," he said.

"The contradiction is still there."

"We've discussed it."

"If an override can be entered before a passenger requests it, the audit record isn't reliable. That affects more than one flight."

Daniel rubbed his forehead. "You think I don't know that?"

The sudden admission startled her. She remained silent.

"We have a backlog. We have pressure to cut handling time. The stations complain whenever we question them. Senior leadership wants reports showing faster boarding. Nobody wants another exception category."

"So we call errors customer requests?"

"I didn't say that."

"Then why won't anyone answer the question?"

Daniel pushed the email back across the desk. "Because the other passenger is connected to people on the board. That's the reality."

Priya looked at him for a long moment. "And what is our responsibility?"

He looked away. "Our responsibility is to keep the system working."

"A system that records things that didn't happen isn't working."

The conversation ended badly. Daniel told her to take a few days off the case. Priya returned to her desk and began searching the approved internal policy library — not other passenger records, which she had no right to browse, but the rules themselves. She wanted to know exactly what the company required when a seat change was disputed. The manual was unambiguous: a voluntary change needed affirmative consent; an involuntary downgrade required compensation processing and a reason code; a safety-related relocation required supporting crew documentation.

Flight 602 fit none of those categories.

She submitted a new report through the protected ethics channel. This time she limited it to process: possible misuse of a voluntary downgrade code, and a potential failure of independent review. She named the earlier ticket references and asked that the matter be assigned outside customer strategy.

By the next morning she had an appointment with the company's internal audit director, Helen Park.

Helen's office was small for someone with such a senior title. Books stood in uneven stacks beside a printer, and the only decoration was a framed photograph of a mountain trail. She read Priya's chronology carefully, asking questions about what the system could and could not prove.

"Do you know whether someone intentionally falsified a record?" Helen asked.

"No. I know the stated reason is inconsistent with the passenger's account and the timing."

"Good distinction. Who else has access to your report?"

"My manager and customer strategy. Possibly the station."

"Have you made copies of passenger information outside approved systems?"

"No."

"Good. Keep it that way. This needs a controlled review."

Priya felt her shoulders loosen for the first time in days. Somebody was finally treating precision as a strength rather than an inconvenience.

Helen opened a fresh case. She directed a small team to preserve the relevant reservation audit trails, review staff access logs, and obtain crew reports through authorized channels. She also requested a comparison of how other involuntary downgrades had been coded over the previous quarter — using an appropriate sample, and proper privacy safeguards.

The team she assembled was small on purpose: two auditors, one data specialist, and Priya, seconded part-time because she knew where the inconsistencies lived. Helen set the rules on the first day and never repeated them: no leaks, no conclusions in email, no passenger data outside the case file, and every claim tied to a record that could be produced. "We are not building a story," she told them. "We are building a floor. Stories can be argued with. Floors just hold."

Priya had worked under managers who treated investigation as public relations with extra steps. Helen treated it as carpentry. It was the first time in Priya's career that the work felt the way she had imagined it would when she chose it.