Marcus listened without interrupting.
"I imagine your foundation has helped many students," Evelyn continued. "But I wonder how often people who fund opportunities stop to consider the small ways they might discourage someone from accepting one."
Marcus thought of the scholarship brochures carrying his company's name.
"I haven't considered that enough," he admitted.
Amara glanced up.
She had not expected him to continue the conversation with Evelyn, much less acknowledge that he had something to learn.
Marcus turned toward her.
"May I ask you about your project again?"
Amara closed the notebook.
"Why?"
"Because I'm interested in the engineering. And because I realize that being interested in your work doesn't give me the right to demand that you show it to me."
She studied him.
"What would you do with the information?"
"Nothing without your permission. I would simply like to understand what you've been working on."
Amara looked at Evelyn, who gave her a small, encouraging nod without answering for her.
After a moment, Amara opened the notebook.
She turned it so that Marcus could see the drawings, keeping one hand on the page.
The project was called AquaWatch.
It consisted of a compact sensor unit, a simple alarm, and a diagram showing how several units could be installed near pipes in older apartment buildings. If moisture appeared where it should not, the sensor would send a signal to a small receiver.
The purpose was to identify leaks before they became expensive structural problems.
"My building has had water damage three times," Amara explained. "The last time, my neighbor's ceiling collapsed in the kitchen. Nobody was hurt, but the repairs took weeks."
Marcus leaned forward.
"So you designed this because of that?"
"Partly. I wanted to know whether a simple device could alert people earlier. Some systems are expensive, and not every building can install them."
"What was the biggest technical problem?"
"False alarms. Condensation sometimes triggered the first version. I had to adjust the sensor placement and rewrite part of the control logic."
Marcus examined the diagram.
"How did you test the revised design?"
Amara described a series of experiments using controlled amounts of water, different surfaces, and varying levels of humidity. She had kept a spreadsheet of results and asked the repair-shop owner to check her wiring.
She explained that the prototype still had limitations. It was not ready for commercial use, and she had not yet tested it in a real building for an extended period.
"But I think the next version could be smaller," she said. "And cheaper."
Marcus looked at the notebook for a long time.
He had invested in companies that spent millions developing devices with far less practical purpose.
Amara's project was not valuable because it was finished.
It was valuable because she had identified a problem, designed a possible solution, tested it, and documented what remained uncertain.
She had done what good engineers did.
"That's thoughtful work," he said.
"Thank you."
"I mean it. You've approached the problem carefully."
Amara smiled, but she did not become suddenly effusive. She returned to the diagram and explained one of the sensor configurations.
Marcus asked questions. This time, he listened to the answers.
When the conversation ended, he leaned back.
"Do you know what I find most impressive?"
Amara shook her head.
"You know what you don't know."
She considered that.
"My teacher says that's where learning begins."
"Your teacher sounds wise."
"She is."
Marcus smiled.
For a few minutes, the cabin became what it should have been from the beginning: a place where two people could speak without one demanding that the other prove a right to be there.
But the story was not finished.
An apology had opened a door.
What Marcus chose to do after leaving the aircraft would determine whether he had learned anything from walking through it.
As the flight approached Los Angeles, Marcus received a message from his assistant.
The meeting he had been traveling to attend had been postponed. A major investor was delayed, and the executives had agreed to move the discussion to the following morning.
Marcus stared at the message.
For weeks, the meeting had dominated his schedule. He had rearranged calls, canceled a family dinner, and insisted on taking the earliest available flight.
Now the urgency had vanished.
He looked across the aisle at Amara.
She was checking her documents again, making sure the notebook, boarding pass, and scholarship confirmation were safely stored.
He thought about the institute's program.
Then he thought about his company's foundation.
A few months earlier, the foundation's board had discussed a proposal to fund practical science projects at under-resourced schools. The proposal had been approved in principle but delayed while the team debated which institutions should receive grants.
The delay had seemed reasonable at the time. The board wanted measurable results, reliable partners, and a process that would satisfy its auditors.
Marcus had agreed with every concern.
Yet he had not once asked whether students who could benefit from the funding had been consulted.
He opened a note on his phone and wrote three questions.
How were applicants selected?
What prevented talented students from participating?
How could the foundation support early-stage projects without forcing young inventors to navigate an unnecessarily complicated process?
He did not write Amara's name.
He did not want her to become a convenient example used to justify a decision he had already made.
Instead, he began thinking about how the foundation could evaluate its own procedures.
If the application process favored students whose schools had experienced grant writers, then the foundation might be measuring administrative resources rather than potential.
If interviews rewarded polished presentation more than careful reasoning, then students with less experience might be underestimated.
If funding required expensive equipment before a project could begin, then the program might exclude the very people it was meant to help.
These were questions worth investigating.
Marcus had spent years asking businesses to identify inefficiencies in their operations.
He had never thought to apply the same scrutiny to his charitable work.
"May I ask you something?" he said to Amara.
She looked up from her papers.
"Yes."
"When you applied to Westbridge, what made the process difficult?"
Amara thought carefully before answering.
"The hardest part was knowing what the application wanted. I had never applied to a program like that before. The instructions used words I didn't understand, and I wasn't sure what counted as a serious project."
"What helped?"
"My teacher. She explained the instructions. The repair-shop owner let me use tools. My mother helped me organize the deadlines."
"And if you hadn't had those people?"
Amara looked toward the window.
"I might not have applied."
Marcus absorbed the answer.
"Do you think other students have good ideas but never apply?"
"Of course."
"How could a program reach them?"
Amara hesitated.
"Maybe by visiting schools instead of waiting for students to find the application. Maybe by allowing teachers to recommend students who don't know how to describe their own work yet. And maybe by giving people small grants to build a first version before asking them to compete for a bigger one."
Marcus wrote the suggestions down.
"Those are useful ideas."
"They're only ideas."
"Most useful plans begin that way."
Amara returned to her papers.
Then, after a moment, she added, "But please don't use my story without asking me."
Marcus put his phone down.
"I won't."
"I don't want people to turn what happened today into a story about how a rude man discovered a brilliant girl and saved her."
The directness of her words surprised him.
"What would you want it to be about?"
"About why you thought I didn't belong before you knew anything about me."
Marcus had no answer.
Amara continued.
"And about how many people might never get a chance because nobody asks them what they're capable of doing."
He looked at the questions he had written.
They suddenly seemed less like a plan for a charitable initiative and more like the beginning of an obligation.
"You're right," he said.
Amara shook her head slightly.
"I don't need you to say that just because you feel bad."
"I'm saying it because I think you're right."
She considered him for a moment.
Then she nodded and returned to her notebook.
Marcus understood that her trust, if it ever developed, would not be purchased by a generous gesture.
It would have to be earned through consistent behavior.
For a man who was used to measuring progress in financial returns and quarterly targets, the lesson was unfamiliar.
It was also necessary.
The captain announced their descent shortly after noon.
Passengers closed their laptops, returned their seats to the upright position, and checked the overhead compartments. The cabin filled with the small sounds of an approaching arrival: buckles clicking, bags being zipped, and people exchanging final remarks.
Amara placed her notebook in her purse and checked her boarding pass one last time.
She was nervous again.
Not because of Marcus.
She had never visited California before. Her scholarship program would bring her into a group of students from different states and countries, many of whom had attended expensive schools and worked with equipment she had only seen in photographs.
She wondered whether she would understand the instructors.
She wondered whether her project would seem too simple.
She wondered whether the other students would already know everything she had spent years learning.
Then she remembered her mother's words.
You do not have to know everything before you begin.
The aircraft descended through a layer of white clouds. Sunlight flashed across the wing, and the city appeared below them in a patchwork of streets, buildings, and green spaces.
Amara pressed her hand against the armrest.