Anger could make a person feel powerful while narrowing the field of vision. She needed to see the entire system, not merely the people standing closest to the damage.
"Let's establish what we know," she said.
Olivia looked up from her notes.
"The original passenger manifest was created yesterday at 4:12 p.m. Eastern time. It identifies you as the principal passenger, with Catherine listed as your ground contact. The aircraft registration and trip authorization match the records held by our company."
"And the revision?"
"Submitted at 8:57 this morning through an external administrative account."
"At 8:57," David repeated. "Less than an hour before boarding."
"Correct."
"Who submitted it?"
"That is still being established. The user account belongs to an employee of Meridian Flight Services, a contractor used by the aviation provider for document processing."
Diane leaned back slightly.
"Was the account authorized to change the passenger manifest?"
"Not independently," Olivia said. "The account could prepare a proposed revision. A separate approval was required before the change became operational."
"Who approved it?"
"At present, the record shows a supervisory approval token associated with the provider's operations system. We haven't confirmed which individual was using it."
David frowned.
"Could the token have been compromised?"
"Yes," Olivia said. "That possibility remains open. We also have to consider whether someone with legitimate access used it improperly. We should not decide between those possibilities until we have the authentication logs."
Diane nodded.
"Good. What did the revision actually change?"
Olivia shared the document.
The original manifest listed Diane Cooper as the principal passenger, with her corporate identification and the authorization reference for the trip.
The revised version did not remove her name entirely. Instead, it changed her status to PENDING EXECUTIVE VERIFICATION and inserted a note indicating that boarding should be denied until a senior operations representative confirmed her authority.
A second note appeared in the internal comments field.
IDENTITY PRESENTATION DOES NOT MATCH EXPECTED EXECUTIVE PROFILE. MANUAL REVIEW REQUIRED.
Diane read the sentence twice.
No one spoke.
David's expression changed first.
"What does 'expected executive profile' mean?"
"We don't know yet," Olivia replied. "It could refer to a legitimate verification discrepancy, but the language is unusual. It doesn't identify a document, a missing credential, a security alert, or a specific inconsistency."
"It describes a person," David said.
"It appears to," Olivia agreed.
Diane looked at the screen.
There it was.
Not a direct slur. Not an explicit statement that a Black woman could not be a billionaire. Nothing so crude that it would immediately resolve every question.
Just a phrase that could be defended as procedure while carrying an assumption no one had bothered to explain.
She had spent years in rooms where people asked whether she was the assistant, the note-taker, the technical consultant, or the person sent to deliver a message.
She had learned to distinguish a single awkward interaction from a pattern. She had also learned that patterns rarely announced themselves as patterns. They appeared in records, repeated decisions, unexplained exceptions, and the testimony of people who had once believed they were the only ones experiencing them.
"Has this wording been used before?" she asked.
Olivia paused.
"We haven't searched the historical logs yet."
"Then do so. Search the phrase, its variants, and the manual-review category. I want the results for every passenger, not just for me."
David nodded.
"I'll have our audit team coordinate with the provider."
"Make sure they don't limit the search to incidents classified as discrimination. If the system was designed to classify the conduct differently, that filter will miss it."
"Understood."
Catherine's voice came through the speaker.
"Diane, there's another issue."
"What is it?"
"The termination notices."
"Go ahead."
"They were not generated through the provider's normal human resources workflow. The initial email came from an automated account used for urgent staffing actions, but the underlying request appears to have been created by someone with access to a restricted administrative function."
Olivia straightened.
"Do we know who?"
"Not yet. The account's displayed name is Operations Compliance, but that doesn't tell us who used it. The provider is supposed to retain the originating user ID and the approval chain."
Diane's expression remained calm.
"Could the notices have been triggered automatically by the manifest dispute?"
"Not according to the documentation Catherine has," Olivia said. "A passenger authorization hold should not generate employment termination notices. Those are separate systems."
"Then we have two events," Diane said. "A questionable change to my authorization and an unusual employment action against the crew. They may be connected, but we don't assume they are."
David rubbed his forehead.
"Someone could have panicked and tried to contain the incident."