At 6:15 she emerged holding a coffee mug that had been empty for probably 40 minutes. There’s a secondary review in 3 weeks, she said, setting the mug on the edge of his desk without looking. The committee wants supplemental documentation on the security architecture. I’ll start building the framework tonight. She stopped. Actually stopped.
And looked at him. Tonight? I work better when I’m ahead of it. I’ll send you a structure draft and you can tell me what’s wrong with it. What if nothing’s wrong with it? Then you’ll tell me it’s fine and I’ll know I got lucky. The corner of her mouth moved. Not a smile, not quite, but a shift in the same direction.
It was the first time he’d seen something approaching that and it was gone before he could fully register it. Don’t send it after 9:00, she said. I don’t read anything after 9:00. You’ve been responding to emails at 11:00. That’s different. How is that different? It just is. She picked up her empty mug. Don’t send it after 9:00. He didn’t send it after 9:00.
He sent it at 8:51 and by the time he was on the subway with Mia’s backpack on the seat beside him and his jacket folded across his knees, his phone buzzed. Three issues with the framework. I’ll mark them in the morning. The structure is otherwise workable. As He looked at that message for a long time. Otherwise workable.
From Ava Sinclair. At 8:59 on a Thursday night, he typed back, I’ll fix the three issues before you see the marks. She didn’t respond, but she read it. He could see the delivery confirmation. He pocketed his phone and leaned his head back against the seat and thought about Jenna’s half sentence and Victor’s shoulder clap and the particular quality of the word trust when it came from someone you weren’t sure you trusted.
He found the first discrepancy on a Friday afternoon, 3 weeks into the job by accident. He’d been pulling archived financial summaries for the security architecture documentation when he turned up a file that was mislabeled, a quarterly report from 3 years ago tagged under a project name that didn’t exist in the current system.
He almost moved past it. He should have moved past it. But the project name, Meridian phase two, appeared twice more in adjacent files and then a third time in a personnel transfer record from the same quarter. And the name attached to those transfers was not one he recognized from the current org chart. He opened the personnel record.
Three names. All reassigned from the core AI development team. The reassignment was logged under a routine restructuring justification. But the timing was off. The restructuring had been announced 2 weeks after these transfers, not before. He sat with that for a while. Then he searched Meridian phase two out in the archived email system.
He had administrative access as part of the EA role and found seven emails. Four were routine. One was a calendar invitation. Two were from a sender address that was no longer active in the system. A deactivated account that had belonged to someone named Dominic Reyes. He looked up Dominic Reyes in the company directory. Not found.
He looked in the archived personnel files. Former senior engineer, development team. Left the company voluntarily, the record said, in the same quarter as the transfers. The exit interview was three lines. It said, “Employee expressed satisfaction with his tenure and wished the company continued success.” That language, that specific corporate emotionless template, he’d seen it before in places where exit interviews were being used to cover departures that hadn’t actually been voluntary.
He leaned back in his chair. I was looking at 3 years of company history through a 2-in window, and he might be completely wrong. File mislabeling happened. Personnel transfers happened ahead of official restructuring all the time. Exit interview templates were genuinely just templates. But he printed the documents.
He made copies. He put them in the back section of the filing folder he kept in his bottom desk drawer, behind the restaurant list he’d updated, and behind the Singapore call protocol. He put them there and he didn’t say anything about them. Not yet. Not until he knew what he was looking at. The second discrepancy turned up on Tuesday.
He found it inside the technology attribution records for the company’s flagship algorithm. The one that had landed the government contract, the one that was the centerpiece of every investor deck and press release and presentation. The attribution records were supposed to document which engineers had contributed to which components for both intellectual property purposes and compensation tracking.
There was a gap. A real one, not a mislabeling. Claude’s response was interrupted. Try again. The gap in the attribution records wasn’t subtle once he knew what he was looking at. It was a clean removal, not missing data, not corrupted files, but a deliberate overwrite. Someone had gone into the records and replaced three engineers contribution logs with a single consolidated entry credited to the core leadership team.
The original timestamps on the files had been altered. The backup copies, which should have been in the compliance archive, had been deleted. Ethan sat at his desk and read through it three times. He wasn’t a forensic accountant. He wasn’t a lawyer. He was an executive assistant who had spent six years in corporate administration and who had learned in that time that the most dangerous things in any company weren’t the loud problems, the failed launches, the public disputes, the budget shortfalls. The dangerous things were
the quiet ones, the ones that had been made quiet deliberately. He printed everything, added it to the folder behind the restaurant list. Then he went looking for Dominic Reyes. It took him four days spread across lunch breaks and late evenings after Mia went to sleep. Reyes wasn’t hard to find.
