Benjamin looked at him.
"What do you mean?"
"You could have left. You could have told everyone who you were and made sure Craig regretted it."
Benjamin considered the question.
"I thought about leaving."
Daniel looked surprised.
"I did," Benjamin continued. "Not because I was ashamed. Because I wondered whether remaining here was worth the effort."
"What changed your mind?"
Benjamin looked through the glass wall toward the corridor.
A maintenance technician was pushing a cart carrying replacement lighting equipment.
"People like Patricia. People like Samuel. People like you."
Daniel followed his gaze.
"They didn't have the authority to change what was happening. But they had been carrying the consequences."
Benjamin turned back.
"If I walked away because one man treated me badly, the people who had been ignored for years would still be here."
Daniel nodded slowly.
"That makes sense."
Benjamin placed a hand on his shoulder.
"But I want you to understand something else. You don't owe this building your suffering. You have the right to leave a workplace that doesn't respect you."
Daniel looked at him.
"Then why did you stay?"
"Because I chose to."
There was a difference.
Benjamin wanted Daniel to understand it.
A person could remain in a difficult place because they felt trapped.
Or they could remain because they believed their presence might help create something better.
Those were not the same thing.
Meanwhile, the independent audit had reached another stage.
Rebecca Shaw and Arthur Collins had reviewed the original invoices, purchase orders, payment confirmations, and work completion records.
They discovered that several companies had submitted invoices using nearly identical templates.
Some invoices included vague descriptions such as emergency operational support, facility optimization, or specialized maintenance services.
Those descriptions were not inherently improper.
But they made verification difficult.
In one case, a vendor billed Pinnacle Tower for equipment installation on a floor where no installation had occurred.
In another, an invoice included labor charges for a weekend when the building's access records showed that no contractor had entered the relevant mechanical room.
The total value of the questionable transactions continued to grow.
By Tuesday afternoon, the review team had identified approximately $1.47 million in payments requiring additional documentation or verification.
Rebecca presented the updated findings to Naomi.
"We have separated the transactions into three categories," she explained.
"First, payments where the work appears to have been completed but documentation is insufficient. Second, payments where the scope of work differs from the original authorization. Third, payments where we cannot currently verify that the services were delivered."
"How many fall into the third category?" Naomi asked.
"Twenty-six transactions."
"And the value?"
"Approximately six hundred thousand dollars."
Naomi studied the report.
"Do we have evidence that Kenneth knew the work was not completed?"
"Not yet."
"Craig?"
"We have evidence that he authorized certain documentation procedures and discussed processing paperwork before inspection. But we still need to establish what he knew about each individual invoice."
Naomi nodded.
"Continue."
Rebecca turned to another page.
"Victor Lane appears in several email chains. He coordinated vendor documentation, communicated with Craig, and received copies of certain approval requests."
"Has he responded?"
"He has agreed to provide a statement, but he wants his attorney present."
"That is his right."
Arthur closed the folder.
"We should also examine the role of the outside contractors. If the invoices were inaccurate, we need to determine whether the errors originated with vendors, internal employees, or both."
Naomi looked at the documents.
"Then we expand the review."
On Wednesday morning, Kenneth Sterling submitted his written response.
He denied knowingly approving inaccurate invoices.
He explained that his department relied on completion certificates and departmental authorization forms.
He also acknowledged that several payment approvals had been processed under unusually compressed timelines.
In his statement, he wrote:
The finance department was expected to maintain operational continuity. I believed the documents submitted to us were accurate and properly authorized.
Rebecca reviewed the statement.
"It is possible," she said.
Naomi looked at her.
"You believe him?"
"I believe we should test his explanation against the records."
Arthur added, "The approval process may have been flawed even if Kenneth did not knowingly participate in misconduct."
That distinction mattered.
A broken system could cause serious damage without every person involved understanding how it had happened.
But the possibility of an innocent explanation did not eliminate the need for accountability.
Later that day, Rebecca identified an email from Kenneth to Craig.
The subject line read:
Quarter-End Vendor Processing
Kenneth had written:
Please make sure all outstanding invoices are submitted before the reporting deadline. Finance needs the supporting documentation in place.
Craig replied:
We are working through the remaining certificates.
Kenneth responded:
I need the files complete before close.
The email did not establish wrongdoing.
It could have been an ordinary request to meet a reporting deadline.
But another message, sent two days later, raised a different question.
Craig wrote:
Some inspections are still pending. We can attach the completion confirmations once the vendor sends them.