The incident had taken place on a commercial flight. It involved a seat, a few minutes of confrontation, and several employees who had apparently decided that one passenger's comfort mattered more than another passenger's confirmed reservation.
Yet Nathan knew that the most important question had not been answered.
Would those employees have treated him the same way if he had looked wealthier?
Would they have spoken differently if he had been wearing a company badge, a military uniform, or an expensive suit?
Would they have questioned their decision if Tyler Prescott had been the man in the plain blazer?
He could not know their private thoughts.
He could, however, examine the behavior.
And he could examine the system that had made the behavior seem acceptable.
Nathan rinsed his coffee cup and set it in the dishwasher.
Then he went upstairs, changed into a charcoal suit, and collected his laptop bag.
At seven thirty, he was already on his way to Whitmore Systems headquarters.
The building stood in a business district where glass towers rose above carefully maintained sidewalks and landscaped plazas. The company occupied twelve floors of one tower, with its engineering teams spread across several departments and its operations center running around the clock.
From the street, Whitmore Systems looked like any other successful technology company.
Inside, however, the organization had been built around a philosophy Nathan had defended since its earliest days: if a company wanted to understand how people were treated, it needed to understand the systems that shaped their decisions.
A scheduling algorithm could quietly distribute undesirable shifts to the same group of workers.
A maintenance dashboard could make one aircraft appear more urgent than another because the wrong metric had been prioritized.
A customer-service procedure could reward employees for satisfying the loudest customer rather than the customer who was actually entitled to help.
None of those outcomes required someone to announce a malicious intention.
Sometimes all it took was a poorly designed incentive, an unquestioned assumption, and a supervisor who preferred not to challenge either one.
Nathan had seen it happen in logistics companies, hospitals, airports, and corporate offices.
He had built his business partly because he believed that better systems could make such failures easier to detect.
That belief was about to become personal.
At 7:42, he entered the executive conference room.
Daniel Harper was already there.
Daniel had been Whitmore Systems' chief operating officer for six years. He was forty-six, broad-shouldered, and usually carried himself with the measured impatience of someone who had learned to recognize a preventable problem before everyone else noticed it.
A laptop sat open in front of him. Beside it lay a printed contract summary, several financial reports, and a legal pad covered in handwriting.
He looked up as Nathan entered.
"You're early."
"So are you."
"I've been reading the Blue Ridge agreement."
Nathan pulled out a chair.
"That sounds like a pleasant way to spend a Monday."
"It became less pleasant around page fourteen."
Daniel turned the contract summary toward him.
"Before we get into the details, I want to make sure we're talking about the same thing. You want a complete review of our relationship with Blue Ridge Airways. Every contract, every amendment, every support arrangement, every service credit, every exception we've made."
"Correct."
"And you want the review to begin immediately."
"Yes."
Daniel studied him for a moment.
"How much of this is about the flight?"
Nathan did not answer immediately.
"All of it began with the flight," he said. "That doesn't mean the conclusion has to be about the flight."
Daniel leaned back.
"That sounds like something you say when you already know what conclusion you want."
"Then let me be more precise. I don't know whether we should renew the contract. I don't know whether the relationship is worth preserving under different terms. I don't even know whether the flight attendants and ground supervisor reflect a wider company culture or simply made a series of poor decisions under pressure."
He paused.
"What I do know is that I want the facts before we decide what the relationship is worth."
Daniel nodded slowly.
"That's reasonable."
Nathan opened his laptop.
"Let's begin with the contract."
For the next forty minutes, they worked through the agreement.
Whitmore Systems had signed its first contract with Blue Ridge Airways nine years earlier. At the time, Blue Ridge had been a growing regional carrier attempting to modernize an aging operational infrastructure.
Its scheduling systems were fragmented. Maintenance teams worked from overlapping databases. Crew assignments were sometimes delayed by manual approval processes. Managers struggled to understand why one disruption could spread through an entire day's flight schedule.
Whitmore had offered a platform that connected those separate systems.