The words bothered her because she could not determine whether he believed them. She started keeping a personal work journal of unusual incidents, recording dates and reference numbers but not copying protected passenger details. A senior crew member cautioned her that Ryan was close to people in corporate revenue operations, a relationship that made him unusually difficult to challenge. "You can be right," the woman said, "and still find yourself with a schedule designed to make you quit."
Anna Desai knew the same pressure from a different side of the airport. She spent her mornings in a low-ceilinged operations room where monitors displayed departures, seat counts, crew connections, and irregular-operations alerts in colors that changed faster than any person could interpret without training. Her colleagues sometimes called her the archivist because she believed every unexplained correction needed a reason. Anna didn't think technology was inherently trustworthy, only that properly preserved records could be better witnesses than memories when people disagreed.
Three years earlier her younger sister, Priya, had been due to travel home for their grandmother's final birthday. At the gate, Priya's paid reservation inexplicably turned into a standby request, and she spent fourteen hours trying to establish that she had done nothing wrong. She arrived after the family had finished the celebration, embarrassed and angry, and eventually accepted a modest voucher because she was too exhausted to continue fighting. Anna remembered the way Priya said, "They kept explaining their screen to me like I wasn't the person who bought the ticket."
The experience hadn't made Anna a crusader. It had made her attentive to the point where a human choice became disguised as a system decision. She knew that a reservation could change innocently through a canceled leg, a schedule swap, or a legitimate request, but all such changes should leave a trace. If a system displayed an approval, there ought to be an authentic customer interaction behind it. If a fee changed, there ought to be a documented reason and a destination for the resulting money.
At first she discovered only tiny inconsistencies: a customer-initiated change recorded without a matching call, a gate override performed during an employee's approved vacation, a refund marked complete that had no corresponding credit to the passenger. Each discrepancy looked too small to matter alone. She flagged them internally and received polite replies saying they reflected reconciliation delays. After the seventh, she asked a supervisor to place a temporary preservation hold on the relevant logs, and that request was quietly rejected.
What finally frightened her was the response she received from Kevin Stone. She had asked him why a sequence of exceptions displayed his user credentials while originating from a shared terminal at Gate 12. Kevin appeared at her desk the following morning with a smile that did not reach his eyes and a printout of her own inquiry. "You're making a lot of noise about routine adjustments," he said. "People who understand the whole business don't get excited about a few lines in a report."