Several weeks later, Nadia discovered the same vendor issue had resurfaced in another area of the company. She and Callan spent two evenings after hours preparing a cross-department analysis, taking care not to alarm the client-service staff until they understood the impact. Their findings were not catastrophic, but they were serious enough to demand formal attention: more than one team was relying on the same vendor assurance without realizing that assurance had never been independently verified. They drafted a recommendation to limit new transactions through the affected route until additional controls were installed. Blaine forwarded the document with a reassuring summary stating that the matter was being monitored and that no immediate action was necessary.
"He didn't say we recommended a limit," Nadia told Callan afterward. She sat opposite him in the nearly empty cafeteria, turning her paper cup between her fingers. "He made it sound like we had agreed the risk was tolerable."
Callan opened the original email on his phone, then the version sent upward. The difference between them was not a typo or an innocent simplification. It was a decision to remove the one sentence that would have forced someone above Blaine to make a difficult choice. He saved both versions, sent a written clarification, and started maintaining a separate index of recommendations that were altered after leaving his desk.
There were other cracks. The procurement team entered contracts without involving technology until after the vendor had begun work, and finance approved payment schedules that did not match the dates on which services were actually delivered. Client commitments changed during sales negotiations, but the changes were not always reflected in the software that generated invoices or settlement instructions. To the outside world, Ashford Meridian looked like a company moving smoothly through complex markets. Inside, Callan found a collection of departments doing their best work in isolation, connected by fragile arrangements nobody had been given the authority to redesign completely.
Miriam Vale recognized the problem better than most, but her days were consumed by funding forecasts, reporting deadlines, and managing the consequences of decisions that arrived in her office already made. She was capable, skeptical, and uncomfortable with explanations that relied on titles rather than numbers. Once, after Callan identified a mismatch between promised client withdrawals and expected cash inflows, she invited him to present directly to her team. He explained the exposure on three ordinary sheets of paper, placing the relevant dates side by side until the risk became obvious. Miriam asked why she had never seen the analysis before. Callan told her it had been submitted through the usual channel months earlier.
"And Blaine?" she asked. Callan hesitated, unwilling to accuse someone based only on the fact that a report had been filtered. Then he gave the narrowest truthful answer he could.
"He disagreed with its priority." Miriam studied the dates again, made a note, and asked him to send future warnings about liquidity timing directly to her office as well as through operations. That request became the beginning of a quiet working relationship between two people who cared more about whether the cash arrived on Thursday than whether a presentation said it would arrive eventually. It also made Callan more visible to Blaine, who did not appreciate questions escaping his preferred channels.