Chapter 60
The Corrupted Number
The most dangerous number in a company is the one everyone has agreed not to question.
At four thirty, that number is thirty percent.
Rina Shah writes it on the glass wall of my conference room and circles it twice. Nico stands near the windows, reading the same benefits report for the third time. Adrian sits at the table with his jacket draped over the chair beside him, which means he expects this meeting to last through dinner.
I have given them access to everything.
That decision should not feel radical. It does because my first instinct was to take the files home, lock the door, and find the answer before anyone could see that I did not have it.
Mira would recognize the instinct. She would call it protection until I admitted it was fear.
"Start again," I tell Rina. "Assume we know nothing."
She taps the left side of the wall. "This is the dataset used in your approved presentation. It includes two years of claims history, projected enrollment under restored benefits, and the reserve required by the insurer. The assumptions are aggressive but defensible."
Her marker moves to the right side. "This copy was attached to the finance office's hiring-freeze authorization. Same file name. Same summary page. Claims cost is thirty percent higher."
Adrian looks up. "Could Elliot's team have sent an earlier scenario?"
"No," I say. "The earlier scenarios were labeled by date and risk level."
"People rename files."
"Which is why I asked Rina to look at the metadata instead of trusting me."
Rina opens a laptop and projects two columns onto the screen. "The approved dataset was exported from the benefits actuarial model at 6:14 p.m. two days ago. The other copy was created at 9:08 a.m. yesterday. But the altered copy contains tables that were retired three weeks ago. Someone assembled a new file using old data and current formatting."
She expands one row. The difference is not spread evenly across the plan. Emergency claims and specialist care have been inflated, while routine coverage remains almost untouched.
"That makes the plan look unstable without making the manipulation obvious," Nico says.
"Exactly," Rina replies. "A flat increase would be easy to spot. This version imitates volatility. It tells a believable story: restore benefits, attract high-cost claims, lose control of the reserve."
I think of the committee members studying my proposal. A few of them asked careful questions. Others had already seemed prepared to call the program reckless. Maybe they had seen these numbers. Maybe someone had made certain they would.
"Who received this copy?" I ask.
"Board finance, procurement, corporate legal, and two insurance consultants," Rina says. "At least according to the distribution list. We need server logs to know who opened it."
Adrian rubs his thumb along the edge of his phone. "If even one director relied on altered figures during the vote, every decision around the program becomes vulnerable to challenge."
"Including the approval," I say.
"Including the freeze."
Nico stops pacing. "Before the presentation."
"Forty-three minutes before the freeze authorization was drafted," Rina says.
Adrian's expression hardens. "Can you prove intent?"
"I can prove sequence and alteration. Intent requires an audit."
"An internal audit," he says. "Without alerting lenders. If they hear that our claims data may be unreliable..."
"They will hear it eventually," I cut in. "The question is whether they hear it from us or from whoever prepared a board action in advance."
Nico tosses the report onto the table. "Transparency is not a spell. You don't say the word and make the consequences disappear. Benefits projections affect reserve requirements, debt ratios, insurance pricing, and the value of every reform you promised yesterday."
"I know."
"Do you? Because this room is full of people who benefit if your plan survives. Rina advised on the projections. Adrian needs the inheritance structure intact. I need Wondervale to stop becoming the problem that consumes every other division. None of us is independent."
Rina caps her marker. "He's right."
I look at her. "You found the discrepancy."
"That makes me a fact witness, not an independent investigator."
The old version of me would have heard disloyalty in every objection. Today, I hear the shape of the solution.
"Then we hire an outside firm," I say. "One chosen by the audit committee, with a written scope none of us can narrow."
Adrian leans back. "You're willing to let strangers inspect every forecast behind the wage and benefits program?"
"Yes."
"They may find your team made mistakes unrelated to this file."
"Then we correct them."
"The board could use the audit to suspend implementation."
"The board is already freezing implementation."
Silence follows. Nico's mouth tightens, but he gives a small nod.
Rina returns to the projected metadata. "If you open the audit, preserve systems first. Email, shared drives, approval logs, and version histories. No broad accusation. If the person who changed this realizes we know, records may disappear."
I reach for the phone in the center of the table, then stop.
"Who controls the preservation notice?" I ask.
Adrian answers. "Corporate legal."
"And who controls their budget?"
"The board."
Nico looks between us. "Use outside counsel. Narrow instruction, immediate preservation, no family firm."
It is the most useful thing he has said all afternoon.
We draft the authorization together. Rina defines the data systems. Adrian adds lender-notification triggers so we do not accidentally violate a disclosure covenant. Nico insists the audit include procurement approvals because benefit administrators and insurance vendors enter through the same onboarding process.
He also adds badge records for the finance archive and printing logs for the executive floor. Adrian objects that the scope is expanding too fast. Rina settles the argument by separating immediate preservation from later review: keep everything now, inspect only what the evidence justifies.
It is an uncomfortable compromise, which is probably why it is the right one.
I add a clause forbidding me from removing records or witnesses from the audit scope without written approval from the independent committee.
Adrian reads it twice. "You understand this limits you too."
"That's the purpose."
Outside counsel accepts the engagement at five forty-seven. Preservation notices reach twelve system administrators five minutes later, and by six Rina has sent the altered file through a secure evidence portal and received a digital receipt.
My own notice arrives a moment later. It instructs me not to delete messages, replace devices, or discuss witness accounts outside counsel's process. I acknowledge it in front of the others. The rule cannot look different because my name is on the building.
The audit exists now. I cannot bury it, even if the findings destroy my plan.
Nico studies me from across the table. "You didn't ask Mira what she thought."
"She isn't my employee, my adviser, or my permission slip."
"That sounds rehearsed."
"I've had a difficult morning."
For half a second, he almost smiles.
Adrian closes his laptop. "The audit committee will want a preliminary briefing tonight. We need to know who had access before that happens."
Rina clicks through the file history. Most of it is technical noise: automated exports, server transfers, formatting changes. Then she opens the authorization tree attached to the altered dataset.
Three digital approvals appear beneath the finance coordinator's upload. Two belong to systems accounts. The third is a named executive approval.
Rina goes very still.
"What?" I ask.
She turns the laptop toward us.
The final line reads: JONAH REED, SENIOR VICE PRESIDENT, PROCUREMENT: APPROVED FOR BOARD FINANCE REVIEW.
Nico exhales through his nose. Adrian says nothing.
I read the line again. Procurement has no place in a benefits approval, yet Jonah's name is there.