A month later the third failed run caused engineers to recommend wider inspections. They found an additional component with wear outside an accepted range, repaired it correctly, and returned to testing. At the next review, someone observed that the newest response did not occur at precisely the same operating condition as before. The project office answered that the mechanical defect might simply be appearing differently as the configuration changed. The suggestion was plausible enough that the meeting moved forward. Its weakness was that nobody identified what observation would prove the suggestion wrong.
Arthur later recalled feeling relieved each time the team discovered a tangible mechanical problem. Tangible problems could be photographed, repaired, and listed as completed work. An unexplained interaction between a prototype, a test installation, and a measurement system was harder to explain to a board that wanted a schedule. He did not deliberately conceal inconvenient evidence. He allowed each new finding to inherit the meaning of the first. By the time Daniel arrived, the original diagnosis had accumulated so many supporting memos that questioning it felt like questioning the competence of everyone involved.
One engineer, Charlotte Wells, kept a private list of tests she thought needed comparison. She was younger than Arthur but had already spent several years on propulsion projects. The list included sensor orientation, installation changes, and the timing of control transitions. She shared it with her supervisor, who put it in a file marked for future investigation after the next planned repair. Charlotte accepted the delay because there were other critical tasks demanding attention. When she finally saw Daniel's question in Priya's review request, she recognized several items from her list. She felt gratitude, followed by resentment that an outsider's words seemed to carry more weight than hers.
Priya asked Charlotte to join the diagnostic team. Charlotte hesitated and said she was tired of being invited to meetings only after someone else had been given credit for the same concern. Priya admitted that the review process had failed to elevate the earlier questions. She promised that the new review would include Charlotte's original observations and the dates on which they had been recorded. The acknowledgment mattered, though it did not erase the frustration. When Daniel met Charlotte, he told her that he had noticed only the broad difference between two curves. She had already identified several possible reasons for it. Their work became stronger once they stopped measuring who had seen what first.
Charlotte helped the team reconstruct the changing test environment, and her old notes identified a data-processing revision that had been overlooked in the initial scope. She was not interested in humiliating anyone. She wanted the work she had done to make the engine better, even if the company took time to learn how to listen. Years later, when Meridian described the program's lessons to new engineers, Charlotte's list would appear in the training materials alongside the formal review findings. She would insist that the lesson was not that junior employees were always correct. It was that a reasonable question deserved a path to examination regardless of who asked it.