The Approval Loop

On a damp Tuesday night in California, Hana Mercer found the first image in a user report and felt her stomach turn.

Her company ran a public website with a moderation workflow that was supposed to make moments like this survivable: deactivate the account, quarantine the material, preserve the evidence, notify law enforcement, and then alert management. Hana followed the procedure exactly. The account went dark. The images were locked away on the company servers, untouched except by the evidence system. She filed the report to the authorities and, when that was done, sent the required notice to leadership.

She expected a brief acknowledgment. Instead, the CEO replied within minutes.

Alistair Voss wanted a full incident packet, including the images themselves.

Hana stared at the email in her dim home office, exhausted enough that the cursor on her screen seemed to pulse with judgment. She answered carefully: the material was illegal, and she was uncomfortable distributing it.

His reply came back almost immediately, sharp and entitled. He reminded her that he owned the company, that he had a right to see any company information, and that she should stop hesitating and comply.

Hana had worked there long enough to know Alistair liked control the way other people liked oxygen. He wanted updates at impossible hours, demanded instant answers, and acted as if every task in the building existed only until he had personally approved it. Still, this was different. This was not a missing invoice or a broken dashboard. This was child exploitation material.

She sat frozen, wondering whether obeying him would make her complicit and whether refusing would cost her job. There was no in-house counsel to call, no friendly legal department to hide behind. Only a late hour, a horrible email chain, and the growing certainty that the CEO did not need those images for any innocent reason.

By Sunday, she was so tired she forgot what day it was.

On Monday morning, her manager sent a terse message: someone else had delivered the material to Alistair.

An hour later, a detective called to ask clarifying questions about her original report. Hana answered what she could, then mentioned—almost in passing—that the CEO had insisted on seeing the images and had apparently gotten them.

That afternoon, Human Resources scheduled a video call.

The HR director appeared with a printed copy of Hana’s private account. Her stomach dropped. They asked if the account belonged to her. Before she could explain, they told her she was being terminated for disclosing confidential information and for insubordination.

Hana left the call numb, furious, and shaking.

The next day, the detective called again, this time with a different tone. He thanked her. Alistair Voss, he said, was already known to investigators. Officers had searched his home and found far more than the images Hana had reported.

The company, meanwhile, began to collapse under the weight of the man who had run it like a kingdom. So many internal decisions had required his personal approval that payroll stalled, projects froze, and even the accountants stopped knowing what to do next.

By the end of the week, the place that had once seemed so solid was wobbling toward ruin.

Hana updated her résumé and started sending it out. She had been unfairly fired, yes, but there was a strange mercy in the timing: there might not be much company left to sue anyone over by the time the dust settled.

When interviewers asked why she had left, she would have an answer that was impossible to ignore.

And before she shut down her accounts for good, she changed her passwords, closed the laptop, and let herself breathe for the first time in days.