Douglas crossed his arms. "Assign someone else."
Priya looked at him. "We have people who can run tests. That is not the same as having someone qualified to lead this commissioning cycle."
Claire glanced at Mark. "Who is the backup?"
Mark hesitated, and the hesitation told her more than any explanation.
"We do not have one ready for this rollout."
Douglas stepped in. "That is an internal staffing issue. We can solve it."
Priya shook her head. "Not by tomorrow. The vendor can send another qualified lead, but the earliest arrival they gave us is December twenty-ninth."
Claire stared at the date. "Why was there no backup?"
Nobody answered immediately. Mark opened a folder and slid three printed forms across the console.
"There were requests," he said.
Ryan Mercer had submitted them in March, June, and October. Each recommended cross-training additional engineers for commissioning coverage. Each explained the operational risk of relying on one specialist for launch-critical context.
Claire looked at the approval column. Douglas Kaine: cost control. Scheduling pressure. Revisit next quarter.
Douglas cleared his throat. "We were managing resources."
Claire did not respond. Priya opened another file.
"There is more. Before leaving, Ryan uploaded a forty-one-page handoff and validation package. It lists every completed test, every unresolved issue, every configuration change, vendor contacts, rollback criteria, and every remaining step."
Claire looked up. "He did that before the meeting?"
"He started it two weeks ago," Priya said. "He keeps handoff packages current because he thinks any critical process that requires one person to be present is already a weak process."
There was no missing password, no locked folder, no attempt to make himself impossible to replace. Ryan had left the company everything he could leave.
Claire began reading. December tenth: initial failover concern. December twelfth: reproducibility notes. December sixteenth: request for extended interruption testing. December twentieth: cache synchronization hypothesis. December twenty-first: final deployment warning.
"I never saw these," she said.
Mark said nothing. Priya did not need to.
Claire turned to Douglas. "How were these summarized to me?"
"As minor engineering delays, which they were."
Priya's expression tightened. "The final report says Ryan could not recommend production release."
Douglas looked at her. "We do not let engineers set corporate strategy."
"No," Priya said. "We let engineers tell us whether the system they are responsible for has passed engineering acceptance."
The room went still.
Claire pulled up the December twenty-first document herself. The first line sat at the top of the page in plain black text: I cannot recommend production release under the current failover behavior.
Yesterday, Claire had believed Ryan was asking the company to choose his Christmas plans over everyone else's. Now the evidence told a different story. He had asked for backups, documented the risk, worked late to finish before the holiday, and when he left, he had handed over every piece of knowledge he had.
"Can we still meet the client's acceptance criteria by Christmas?" Claire asked.
Priya answered without hesitation. "Not responsibly."