At 11:05, the supplier's compliance office received a separate exception notice contradicting that assurance.
By 11:30, the supplier had stopped initiating new transfers through Ashford Meridian until the discrepancy could be explained.
Anika traced the authorization issue in twenty minutes. Correcting it required cooperation from Legal, the client, and the settlement provider, a process that could not be completed by forcing a status field to change. She asked Blaine to approve the escalation. He told her to classify the event as a routine delay.
"That would be false," she said.
"It would be manageable."
"Those aren't synonyms."
For a moment she expected him to fire her. Instead, he said he would handle the client himself and walked away.
He called Vivian shortly after noon. "A few normal transition issues. Nothing strategic."
She asked whether the team had contacted Callan for clarification.
"Not necessary."
"Good," she said. "I don't want him thinking we need him to keep the lights on."
At 12:38, a second client reported discrepancies in a performance file delivered through the morning distribution process. The file had been generated from valid transactions, but it had paired them with an outdated set of contractual classifications. The figures were close enough to look plausible and wrong enough to violate the reporting standard in the client's agreement.
Maya recognized the pattern. She found the exact warning in Callan's transition notes: If the classification service and settlement feed are on different validation dates, block external delivery pending reconciliation. Do not certify manually without a second reviewer.
Someone had manually certified the file.
The audit trail identified a manager in Blaine's department. When Maya asked him why, he said Blaine had ordered all routine reporting to continue regardless of transition delays.
"I thought the warning was just technical," he said.
"It was technical," Maya replied. "That doesn't make it optional."
At one, a conference call convened in a windowless meeting room. Representatives from Finance, Legal, Operations, Technology, Client Relations, and Strategy crowded around the table. Vivian joined remotely, her camera on, her expression impatient.
"Explain this simply," she ordered.
Marcus spoke first. "The infrastructure is stable. We have authorization exceptions and reporting controls that have been bypassed or left without a trained owner."
"How did that happen?"
"The designated successor was never properly trained."
Blaine cut in. "That's an unfair characterization. Mercer made his documentation intentionally dense."
Tessa, sitting at the far end of the table, opened the training register. "The completion certificate was entered without his signature. The required knowledge-transfer sessions weren't conducted."
"Callan refused to cooperate," Blaine said.
"I have the invitations," Tessa replied. "He accepted every session that was scheduled. They were canceled from your office."
Vivian stared at the screen. She had not expected the attorney to contradict Blaine in public.
"Can we fix the problem today?" she asked.