Sophie adapted faster. She liked that he was home when school ended and that dinner sometimes happened before seven instead of being postponed by traffic from the warehouse. She also understood, more than Ryan wanted her to, that he had lost something.
One evening she sat across from him while he reviewed job listings on his laptop. "Do you miss it?"
Ryan looked up. "Parts of it."
"The machines?"
"The people. Some of the machines."
"Do you miss Claire?"
Ryan nearly dropped his coffee.
Sophie looked genuinely puzzled by his reaction. "She came to the shelter."
"That does not mean I miss her."
"You made the face."
"What face?"
"The one where you pretend a question is weird because you do not want to answer it."
Ryan stared at his daughter. "You are eight."
"I know."
The conversation ended only because Sophie decided her math homework was more interesting than watching him fail to respond.
Claire did not contact Ryan for nearly three weeks after Christmas except through formal channels related to the investigation. She had learned enough from the school lobby not to turn apology into pressure.
Instead she spent January restructuring the launch governance process. Every major deployment would now require a signed technical-readiness statement attached directly to the executive schedule. No COO, vice president, or program director could substitute a summary for the underlying recommendation when risk was unresolved.
Cross-training budgets moved from discretionary department expenses into resilience planning. Mark Ellis was given authority to reject staffing plans that created a single-point human dependency without documented mitigation. Priya became chair of a new technical-readiness council with direct access to the board's risk committee.
The change irritated some executives. Claire expected that.
One senior vice president complained that the new review process would slow decisions. Claire asked him how many days had been lost to the Christmas crisis.
"That is different," he said.
"It is exactly the same," Claire replied. "Speed without context created the delay you are complaining about."
She also changed something smaller and less visible. Every executive staffing packet now included original leave approvals rather than only current availability. Claire had discovered that stripping history from a spreadsheet made human commitments look like blank cells waiting to be filled.
In late January, she met with Mark and Priya to discuss a permanent role focused on reliability, commissioning standards, and training. The job had not existed before the December failure because the company had treated those responsibilities as scattered technical tasks rather than a discipline.
"Ryan is the obvious candidate," Mark said.
Claire looked at him. "Obvious does not mean available."
Priya folded her arms. "He will assume you are trying to buy forgiveness."
"Then we make sure we are not."
They built the role around the work the company actually needed: technical governance, launch-readiness standards, cross-training, vendor qualification, incident learning, and the authority to stop deployment when defined acceptance criteria were not met. Reporting would go through the senior technical executive, not operations.
Claire removed herself from decisions involving compensation, performance evaluation, and hiring approval for Ryan specifically. She asked Evelyn Ross to have the board's compensation committee review the offer to avoid even the appearance of personal pressure.
When the package was ready, Mark called Ryan.