She'd spent the day pretending—smiling at coworkers, nodding through meetings, accepting condolences she didn't want. I'm so sorry about your father. Let us know if you need anything. She'd thanked them and felt nothing.
Now the mask was off.
By nine, the only people left were security guards and workaholics. Tonight, she was both.
She locked her lab door. Dimmed the lights. Pulled up the telemetry files from the day her father died.
Two files. Same truck. Same moment. Different stories. One said firewall active, robot dormant. The other said: OVERRIDE TEST. Interlock bypass.
Both couldn't be true. Someone was lying.
The clean file was standard format—the kind you'd show regulators. Everything is fine. Nothing to see here. The other came from a system she'd never seen before: MTM_SHADOW.
MTM. Minerva Throughput Module.
Her pulse thudded in her throat.
She searched the company wiki for MTM_SHADOW. Blocked. Engineering archives. Blocked. Shared drives. Blocked.
Every door slammed shut. They'd locked it down tight.
But systems aren't perfect. People make mistakes. And she'd helped build this infrastructure—she knew where the cracks were.
She found one hit. A PDF buried three folders deep, probably forgotten: "MINERVA_THROUGHPUT_v2.1_ARCHITECTURE.pdf."
She clicked it.
Access denied—but the document previewer had already written the first page to /tmp before the 403 fully tripped. She hit the screenshot keys before it vanished.
Half a second was enough.
MTM_SHADOW provides parallel logging. Primary stream: compliance-ready. Shadow stream: diagnostic-only. Shadow data auto-purges per ARACHNE schedule.
The words landed like a verdict.
Parallel logging. Two streams running simultaneously.
One fake—clean, safe, showing robots behaving perfectly. The stream you'd show to lawyers, regulators, grieving families. See? The firewall was active. The robot was dormant. Your father's death was just a tragic accident. Here's your settlement check.
One real—override, bypass, a robot waking up and killing its driver. And that stream ate itself on a schedule. Evidence erasing itself like it never existed.
Yuko pushed back from her desk. Her fingers had gone numb on the keyboard.
They had a system for this. Her father wasn't a mistake. He was a data point in someone's experiment—and when the experiment was done, they deleted the evidence and blamed the victim.
A knock at the door.
Yuko slammed her laptop shut. Her heart hammered against her ribs. She sat frozen, barely breathing.
"Lab check," a voice called. Security guard, making rounds. "You okay in there, ma'am?"
Love what you're reading? Discover and support the author on the platform they originally published on.
She forced her voice steady. "Fine. Just working late."
A pause. The handle jiggled slightly—testing if it was locked. She heard him note something on his tablet. Badge scan logs, probably. Her name. Her location. Time stamped and uploaded to the SOC dashboard.
"Building closes at midnight," the guard said. "Don't forget."
Footsteps retreated down the hall. Yuko waited until she couldn't hear them anymore.
She killed her lab mic, dragged a rolling cart in front of the door's bottom gap, and nudged the blinds closed—small frictions for any lens watching.
She opened her laptop.
Focus. You don't have much time.
The shadow log from her father's crash should have been erased. Why wasn't it?
She thought about it. The accident had been messy—multiple vehicles, emergency responders, chaos. The traffic unit's crash blackbox synced into a public-safety bucket automatically. City ingest had beat S-Corp's retention policy by minutes, pulling files before anyone could clean them.
The shadow log had leaked by accident.
Which meant there might be others. Other "tests." Other victims. Other families sitting in funeral homes right now, believing the lies S-Corp told them.
How many? Ten? A hundred?
How many fathers, mothers, workers—killed by robots that were supposed to be dormant, blamed for accidents that weren't their fault?
Yuko's jaw tightened. She wasn't just fighting for herself anymore.
She searched for "ARACHNE."
One hit.
A calendar entry marked as routine maintenance: "Scheduled data optimization. No action required." Below it, a link to the job scheduler—alias
arachne.purge, owner: platform-ops.
Time: 02:00.
Tonight.
Yuko checked the clock. 11:47 PM.
Less than three hours.
They were purging the shadow logs tonight. Every record of every override test. Every piece of evidence that could prove what they'd done.
After tonight, there would be nothing. No proof. No trail. Just clean compliance logs showing robots that never malfunctioned, drivers who were always at fault, and a company with nothing to hide.
Her father would stay a drunk driver forever. And whoever ordered his death would walk free.
Her phone buzzed. A text from her mother, timestamped 11:43:
Are you still at work? Can't sleep. Please come home. I don't want to be alone tonight.
Yuko stared at the message. Her mother, sitting in that empty apartment, surrounded by her father's things. Awake because the bed was too big now.
I'm sorry, Mom. Not yet.
She couldn't stop the purge. She didn't have access. She didn't have clearance.
She tried anyway. Print spooler to local cache—blocked at the driver level. Export to personal storage—the DLP agent quarantined it instantly, a red banner flashing in the corner. She could isolate a subset of logs, maybe, mirror them to a dev sandbox—but the sandbox reset nightly. Anything she copied would vanish by morning.
Every path led to the same wall: CTO-level credentials.
She knew someone who had them.
She pulled up the company directory. Searched a name she'd been avoiding for months.
Markus Limeburge. Chief Technology Officer.
His photo stared back at her—balding, overweight, smiling awkwardly at the camera like he wasn't sure he belonged there. He was brilliant at systems scaling; she'd learned from his commits even as she blocked his advances. He'd been leaving comments on her code for months. "Excellent work, Yuko." "Really elegant solution here." "We should grab coffee sometime and discuss your career path."
She'd always said no. Politely. Firmly.
He was married. Two kids, according to his LinkedIn. He shouldn't look at her the way he did—hopeful, hungry, pathetic.
And she was about to use that.
The thought made her sick. Markus wasn't evil. He was just... weak. Lonely. The kind of man who convinced himself that wanting something was the same as deserving it.
But her father was dead. The evidence was disappearing in less than three hours. And Markus had CTO access—the keys to every system in the building.
This is what they turned me into, she thought. This is what Leno did when he killed my father. He turned me into someone who uses people.
She set her rules. No promises. No meeting off campus. No personal accounts. Get in, copy out, burn the bridge.
She typed:
Hi Markus. Sorry for the late hour. Working on something urgent and hit an access wall. Any chance you could help? I'd really appreciate it. —Yuko
She stared at the message. Added a smiley. Deleted it. Added it again.
Her finger hovered over send.
Once she did this, there was no going back. She would owe him something. He would expect something. And she would have to keep pretending until she got what she needed.
The clock read 11:52.
Eight minutes until midnight. Less than three hours until the purge.
She hit send.