Northgate Hospital’s compliance room did not look powerful. It had two metal cabinets, a scanner, a rectangular table, and a wall clock running three seconds fast. Ruth Kamau placed two items in front of Musa.
On the left was Northgate’s signed 2024 contract pack, stamped at every separator. On the right was a printout of the attachment Musa had sent that morning.
“The original does not leave this room,” Ruth said.
“I don’t need it to.”
“And you will not photograph every page.”
“I don’t need to.”
“What do you need?”
“Version code, clause numbers, page count, approval reference, footer, and a certified comparison if you confirm the differences.”
A procurement clerk brought the custody log. Musa signed that he had viewed the original on site and had not taken a copy. Every boundary mattered now.
The Standard annex was `STD-7.2`, twelve pages. The Blue attachment was `BLU-7.2`, fourteen.
Ruth opened the response-service clause. Standard required replacement within seventy-two hours after a verified fault. Blue promised twenty-four hours, subject to equivalent inventory availability.
“Twenty-four sounds better,” Musa said.
“Until the next paragraph.”
Standard required written approval before an equivalent model could be substituted. Blue allowed an equivalent substitute inside the response window without additional written consent, as long as an internal compatibility checklist passed.
The warranty route also differed. Standard sent claims directly through Meridian’s manufacturer-authorized process. Blue allowed an affiliate service provider to intervene. Freight liability shifted after a particular dispatch scan.
“Had you ever seen Blue before today?” Ruth asked.
“No.”
“Certain?”
“I saw the filename once in shared-folder autocomplete. I was told client files were Standard.”
Ruth pushed an invoice printout toward him. “Three of our dispatch notes carry `BLU-24`.”
“It may be an internal route code. It does not prove contract authority.”
“You sound like you are protecting your company.”
“I’m protecting the line between what we know and what we assume.”
That answer changed the room. Ruth stopped treating him like someone trying to sell an explanation.
The procurement clerk scanned the relevant cover, footer, and clause pages from Northgate’s original and generated a certified comparison sheet with a custody reference. Musa supplied only the attachment hash from his incident record. The hospital did not import his file.
On the approval page, Musa saw initials: `PL`.
“Peter Limo?”
“Your former legal officer,” Ruth said. “He attended our early meetings.”
The approval date bothered her. Northgate’s contact history contained Peter’s farewell email. He had left two months before the date printed beside those initials.
“Does that mean the signature is fake?” Ruth asked.
Musa could feel the temptation to say yes.
“I don’t know. It could be a stale template block, a misused approval mark, or something else. The date mismatch is real. The explanation is not yet proved.”
Ruth folded her arms. “Your company sent a different annex, our invoices contain Blue codes, and an approval mark carries the initials of someone who had already left. What exactly do you expect me to say?”
“Say exactly that. Don’t skip the steps.”
“And what will you say?”
“That a client-side certified comparison confirms material version differences and an approval-date mismatch. I will not call it fraud until the source trail supports that.”
The clerk added the finding to the certified sheet. Musa took only the Northgate-certified copy, because Northgate owned the contract record.
Victor messaged: **Do not discuss internal documents with client without Legal. Return immediately.**
Musa placed his phone face down and completed the scheduled appointment.
Before he left, Ruth opened a purchase-order register on screen. They checked only references already connected to the certified comparison. `BLU-24` appeared on more than one receiving note after the Standard contract had been signed. Musa asked the clerk not to export the whole register. One line was enough: `BLU-24 observed on multiple receiving records; authority not determined.`
Ruth asked if he was afraid of too much evidence.
“I’m afraid of evidence with no scope. If we carry everything, we forget the question we started with.”
As Musa stood, the shame of the morning changed shape. A genuine system problem would not erase the fact that he had clicked Send without checking. He repeated that to himself before returning to Meridian: proof of a broader process was not an eraser for his own mistake.
Ruth touched the approval-date line. “Peter Limo left here two months before this date.”