Grace listened to the explanation without interrupting. When it ended, she asked why Callan's original recommendation to test the gateway had been deferred. Vivian answered that leadership had accepted assurances that were not properly supported and that an independent review was examining how that happened.
Grace asked whether the company intended to publish the control findings to affected partners. Callan described a proposed assurance package with independent validation, clear exceptions, and a timetable for unresolved items. Grace said she would recommend a limited resumption of activity after the evidence was verified. She did not promise the full relationship would return, and nobody tried to extract a promise she was not ready to give.
After the call, Vivian remained in the conference room while the others gathered their notes. "I almost told her everything was fixed," she admitted. Callan closed his laptop. "You would have been wrong," he said.
She looked up sharply, then nodded. "I know." He waited, sensing that she had more to say. She told him she had spent much of her career treating uncertainty as a sign of weakness in the person presenting it. He replied that uncertainty was dangerous only when people pretended it did not exist.
The next morning brought the most serious technical test of the recovery. An automated international transfer batch began generating inconsistent status confirmations under a combination of timing conditions the team had been monitoring. Samir noticed the pattern before the amounts posted to the client-facing ledger. The control dashboard showed an increasing difference between transactions marked ready for release and transactions independently confirmed as ready. It did not prove that funds had been lost, but it indicated that continuing the automated run without review could compound the uncertainty rapidly. Samir called the incident team and asked for an immediate decision.
Callan arrived in the operations room carrying the current exception list. The monitors glowed under fluorescent lights, and a dozen people stood around desks, arguing in urgent fragments about whether halting the run would trigger substantial fees or damage relationships with counterparties. A treasury manager insisted the company could not afford a delay. Another engineer warned that continuing might create thousands of records requiring later correction. Callan asked the team to separate the costs they could quantify from the exposures they could not yet verify. He listened to the answers and requested confirmation that the protective stop procedure had been tested by the outside specialist.
Samir said it had, but he hesitated when Callan recommended initiating the controlled halt. "Stopping now could cost us several million in timing penalties and emergency liquidity arrangements," he said. "I know," Callan answered.
"Letting unverified transfers cascade across multiple systems could put an unknown amount at risk. We can explain a documented stop. We cannot explain a decision to keep moving because we were afraid of the price of caution." He looked to Miriam, who held the authority to accept the immediate treasury impact. She reviewed the figures, authorized the protective pause, and directed the team to notify the relevant counterparties.