She couldn't blame him. She was also in the spaces around all of this thinking about Caleb Rowan. Not in a way she could easily describe, not as a business problem. She had officially closed his file. The termination stood.
The HR review she'd commissioned had concluded that the firing was procedurally improper, but that Caleb had declined reinstatement, and therefore the matter was resolved as far as the company's legal exposure was concerned. The lawyers were satisfied. The board had stopped asking about it. On paper, the situation with Caleb Rowan was finished. In practice, she thought about the kitchen on Wednesday evenings and what he had said standing at the stove.
And she thought about the file, and she thought about Reyes's voice in the hangar. her the morning she'd fired him. That constrained, careful voice trying to say something that Sloan had cut off before it could form. She thought about all of it the way you think about something that isn't finished just because the paperwork says it is. The thing she kept returning to was the quality of the work. She had managed a lot of engineers over 6 years.
She had hired and fired and promoted and restructured, and she had developed through accumulated experience a reasonably reliable sense of what competence looked like at its various levels. Solid was common. Good was less common. Exceptional was rare enough that you noticed it clearly when it arrived. The way you notice a note played precisely in tune in a room full of instruments that are slightly off.
What the documentation told her about Caleb Rowan's work was that he was operating at a frequency she had almost never encountered. Not because he was flashy. Nothing in the file was flashy. It was the opposite. the precision of the documentation, the fact that he had never missed a recalibration window in 14 years of records, the particular quality of his written findings, which were plain and technical and contained no redundancy and no hedging. He wrote the way a person writes when they are absolutely certain of what they're describing.
She had hired people at three times his salary who could not produce a findings report with that kind of clarity. and he was in a workshop on Meridian Street fixing private aircraft for individual owners and doing by all accounts fine. She wondered sometimes what that felt like to be that good at something and to be doing it in a room that 40 people couldn't see. She suspected he wasn't wondering about it at all. The crisis arrived on a Tuesday in March, which was an ordinary Tuesday in every way until it wasn't. The aircraft in question was a corporate transport, a mid-range twin engine model that Asterion had acquired and was preparing for delivery to a financial services firm whose executives would use it primarily for domestic travel.
It was not as valuable as the Meridian. It was not carrying the same strategic weight, but the delivery deadline was in six days, and the client had already moved the date once, and the senior account manager had made clear, in the gentle but absolute language of someone who had been managing that relationship for 2 years, that a second delay would have consequences. The fault appeared on a Monday evening, first flagged by an automated diagnostic during a routine systems check. By Tuesday morning, it had been through two full engineering reviews, and the result was the same both times. An intermittent electrical fault somewhere in the aircraft's primary avionics bus, presenting irregularly, disappearing before it could be traced, and reappearing in a different configuration each time the diagnostic ran.