There was no dramatic flash of genius. At first he assumed he had misunderstood the meaning of one variable because he had only the displayed equations and no knowledge of the underlying code. He checked the next line and saw that a boundary condition had been written in a form that would allow an unresolved wait to be counted more than once. It was the sort of mistake that a team could stare at for hours when everyone shared the same underlying assumption.
He stood in the doorway for perhaps ninety seconds, long enough to notice two engineers struggling with a simulation and another crossing out a calculation that would not converge. Claire, reviewing a client message near the back wall, looked up and saw him. At first she thought he had come to move the chair and finish his work. Then she recognized the particular expression on his face, and an old memory of him studying a complicated proof returned so vividly that she felt a brief pressure in her chest.
Owen turned toward her. He did not speak, but his expression held a question she understood immediately. Claire could have asked Marcus whether a custodian might offer a mathematical observation, but the room was full of urgent work and she feared the question itself might embarrass Owen. Instead she gave a small nod, not a command or a public introduction, simply permission to speak if he chose.
He pushed the cart clear of the doorway, walked to the whiteboard, and waited until the engineer nearest him stepped aside. "May I use this corner?" he asked quietly.
The engineer glanced at the gray uniform and then at Claire. She nodded again. Owen picked up a black marker and looked once more at the expression in the center of the board.
He wrote seven lines. The first restated the waiting term in a more explicit form; the next separated a completed assignment from one still waiting to close. Two lines established the boundary that would prevent the same delay from carrying into a later iteration. The final expressions isolated the condition under which the optimization would cease to give trustworthy results, and he placed a bracket around the part he believed the team needed to examine.
He stepped back and put down the marker. He had not accessed the company's data, touched its systems, or claimed to know the code. He had identified a mathematical possibility on a board where the variables were already visible, and he looked almost embarrassed by the attention that followed. For a second nobody said anything because the room was still busy doing what it had been doing before he entered.
Ryan Briggs was the first to notice. He stopped speaking to Priya in the middle of a sentence and stared at the black lines beneath the crowded work of the morning. "Who wrote that?" he asked, so loudly that Marcus stopped his telephone conversation. Several people turned to find Owen standing beside the board in his work uniform, the mop cart visible through the open door.
"I might be wrong," Owen said. "I don't know your implementation. But if the error involves the waiting function, that's the boundary I'd check first."