Three days after the incident, Mark received an email from David. Subject: Meeting Request Mark, I'd like to schedule a one-on-one to discuss the review process. Can you come to my office tomorrow at 2 PM? Best, David Mark stared at the email. His stomach tightened. Discuss the review process. That meant explain why you failed. He typed a response. David, I'm available at 2 PM tomorrow. I'll bring my review documentation. Best, Mark He hit send before he could second-guess himself. --- The next day, Mark walked into David's office at 1:55 PM. David was at his desk, a stack of papers in front of him. He looked up when Mark entered. "Close the door." Mark closed the door. He sat in the chair across from David's desk. "Thanks for coming," David said. His voice was friendly, casual. "I wanted to have a more informal conversation about the process. Just to make sure I understand everything." Informal conversation. Mark had been in corporate America long enough to know that nothing was informal when there was a paper trail. "Of course," Mark said. "I brought my documentation." He placed a folder on David's desk. Inside were his review notes, test results, and approval records for the past two years. David glanced at the folder, then back at Mark. "Thanks, Mark. I appreciate you being so thorough." He leaned back in his chair. "I just have a few questions. Just to clarify things for the record." For the record. There it was again. "Sure," Mark said. "What would you like to know?" David picked up a piece of paper from his stack. "I've been reviewing the email trail from the past two years. I noticed something interesting." He slid the paper across the desk. It was an email from Mark, dated six months ago. Subject: Re: Code Review Process David, I've been thinking about our review process. With the volume of code CodePilot is generating, I'm concerned that we might be missing things. Should we consider adding another reviewer or expanding the test suite? Best, Mark Mark stared at the email. He remembered writing it. He had been worried about the workload, about the speed at which CodePilot was generating code. "I remember this," Mark said. "I was concerned about our capacity." David nodded. "And what happened after you sent this?" "I... don't recall exactly." David picked up another paper. "Let me help you remember." He slid another email across the desk. This one was from David, dated the same day. Subject: Re: Code Review Process Mark, Thanks for raising this. I've discussed with leadership, and we're comfortable with the current process. CodePilot has been running for two years without issues. Let's continue as is. Best, David Mark stared at the email. He had forgotten about this exchange. He had raised a concern, and David had dismissed it. "I see," Mark said slowly. "I had raised concerns about the process." "You did," David said. "And I told you to continue as is." "That's correct." David's pen moved across his notebook. "So you were aware of potential issues with the review process, but you continued to follow the same process?" Mark felt the trap close. If he said yes, he was negligent. If he said no, he was lying. "I raised the concern to management," Mark said carefully. "Management decided to continue with the current process. I followed management's direction." David nodded slowly. "I see. And did you document this concern anywhere else?" "I sent the email to you," Mark said. "That's the documentation." David wrote something down. "And after I told you to continue as is, did you have any other concerns?" Mark hesitated. He had had other concerns. He had noticed that CodePilot's code was getting more complex, that the edge cases were harder to identify. But he hadn't documented them. "I continued to have general concerns about the workload," Mark said. "But I didn't raise them formally." "Why not?" Mark's mouth was dry. "I had already raised the issue. Management had made a decision. I didn't want to be seen as not a team player." David's pen moved. "So you were concerned about being seen as not a team player, but you weren't concerned enough to document your concerns?" Mark felt the walls closing in. Every answer was a trap. "I was concerned about the process," Mark said. "I raised it. Management decided. I followed the decision." David nodded. "I see. Let me show you something else." He picked up another paper. This one was a performance review, dated one year ago. Employee: Mark Chen Rating: Exceeds Expectations Comments: Mark has been an excellent Code Reviewer. His attention to detail and commitment to quality have been instrumental in maintaining the integrity of our AI-generated code. "Your performance review says you 'exceed expectations,'" David said. "It specifically praises your attention to detail." Mark stared at the review. He had been proud of it at the time. "I take my work seriously," Mark said. "I can see that." David's voice was neutral. "But if your attention to detail is so excellent, how did you miss an issue that cost the company eighty-seven million dollars?" The question hung in the air. "I relied on the standard test suite," Mark said. "The issue was an edge case that wasn't covered by our tests." "And you didn't think to expand the test suite?" "I raised that concern," Mark said. "Six months ago. You told me to continue as is." David nodded slowly. "I did. But I'm not a technical expert. I relied on your professional judgment." Mark felt the trap snap shut. "You asked if we should add another reviewer or expand the test suite," David continued. "I asked leadership, and they said the current process was fine. But you're the technical expert. You could have pushed back. You could have documented your concerns more thoroughly." "I—" "Instead, you continued with the same process. And now we've had an incident." David's eyes stayed on Mark's face. "I'm not trying to blame you, Mark. I'm just trying to understand what happened. For the record." For the record. Mark was starting to hate that phrase. "I understand," Mark said. His voice was steady, but his hands were sweating. "Is there anything else you need from me?" David leaned back in his chair. "Not right now. I'll follow up with HR and Legal. We'll be in touch." Mark stood up. His legs felt unsteady. "One more thing, Mark." David's voice was casual, but something in his tone made Mark pause. "You mentioned earlier that Sarah Kim sent you some emails about testing. Do you remember those?" Mark's stomach dropped. "I... I don't recall specifically." David nodded. "I'll have Sarah forward them to me. I just want to make sure I have the complete picture." The complete picture. That meant more evidence. "I understand," Mark said. "I'll cooperate fully." "Good." David smiled, but the smile didn't reach his eyes. "I appreciate your cooperation, Mark. This is a difficult situation for everyone." Mark walked out of the office. The fluorescent lights seemed harsher today, casting long shadows. He reached his desk and sat down. His hands were shaking. He opened his email and searched for messages from Sarah Kim. There were dozens. But one stood out, dated three months ago. Subject: Potential Issue Mark, I noticed something in the latest code batch. There's a pattern that might cause issues under certain market conditions. I ran some additional tests, and the results are concerning. Can we discuss? Best, Sarah Mark stared at the email. He didn't remember responding to it. He searched for his reply. Nothing. He had never responded. She warned me, Mark thought. Three months ago. And I didn't follow up. He sat back in his chair. His mind was racing. David knows about this email. He's going to use it. He opened a new message and started typing. To: David Morrison Subject: Re: Meeting Follow-up David, Thanks for the meeting today. I want to follow up on your question about Sarah's emails. I've reviewed my records, and I found an email from Sarah dated three months ago regarding potential issues. I don't have a record of responding to this email. I want to be transparent about this. Best, Mark He read the message three times. It was honest. It was transparent. It was also an admission of negligence. He hit send before he could change his mind. --- That night, Mark couldn't sleep. He lay in bed, staring at the ceiling, replaying the meeting in his mind. David had been friendly, casual. But every question had been a trap. Every answer had been documented. For the record. Mark realized now what that meant. It meant I'm building a case. And you're the target. His phone buzzed. A message from David. Thanks for the follow-up, Mark. I appreciate your transparency. Let's discuss tomorrow. Mark stared at the message. His stomach churned. Tomorrow. Another meeting. More questions. More documentation. He put the phone down and closed his eyes. But sleep didn't come.
The scent of stale coffee hung in the air as Mark walked into the office, each step heavy with dread. His meeting with David was scheduled for 10 AM, but the weight of anticipation made every minute feel like an hour. At 9:45 AM, his phone buzzed. Subject: Meeting Rescheduled Mark, I need to push our meeting to this afternoon. I have a conflict. Can you come at 3 PM? Best, David Mark stared at the email. Relief washed over him, immediately followed by a deeper unease. Why the delay? What's happening behind the scenes? He typed a response. David, 3 PM works for me. I'll see you then. Best, Mark He spent the morning at his desk, trying to work. But his mind kept drifting to the meeting, to the questions, to the paper trail being built around him. At 2:30 PM, he received another email. This one was from Jennifer Walsh in HR. Subject: Meeting Request Mark, I'd like to schedule a meeting to discuss the incident. Can you come to my office tomorrow at 10 AM? Best, Jennifer Mark stared at the email. HR. That meant the process was moving forward. They're building a case, he thought. And I'm the target. --- At 3 PM, Mark walked into David's office. David was at his desk, a new stack of papers in front of him. He looked up when Mark entered. "Close the door." Mark closed the door. He sat in the chair across from David's desk. "Thanks for coming," David said. His voice was still friendly, but there was something different in his eyes. Something harder. "I wanted to follow up on our conversation from yesterday," David continued. "And I wanted to show you something." He slid a piece of paper across the desk. It was an email from Sarah Kim, dated three months ago. Subject: Potential Issue Mark, I noticed something in the latest code batch. There's a pattern that might cause issues under certain market conditions. I ran some additional tests, and the results are concerning. Can we discuss? Best, Sarah Mark stared at the email. He had seen it last night. He had admitted to not responding. "I found this in my records," Mark said. "I don't have a record of responding." David nodded. "I know. Sarah forwarded it to me." Sarah forwarded it. Mark felt a pang of betrayal. He had thought Sarah was on his side. "I should have followed up," Mark said. "I don't have an excuse." David's pen moved across his notebook. "Can you explain why you didn't respond?" Mark thought carefully. He needed to be honest, but he also needed to protect himself. "I receive a high volume of emails," Mark said. "I try to respond to everything, but sometimes things slip through. I don't recall specifically why I didn't respond to this one." "So you're saying you just missed it?" "I'm saying I don't have a record of responding. I may have intended to follow up and forgotten. I may have read it and thought it wasn't urgent. I don't recall." David wrote something down. "Sarah says she followed up with you in person." Mark's stomach dropped. "I don't recall that." "Let me show you something else." David slid another paper across the desk. It was a calendar entry, dated two months ago. Meeting: Sarah Kim - Code Review Discussion Time: 2:00 PM - 2:30 PM Location: Mark's Office Mark stared at the calendar entry. He didn't remember this meeting. "I don't recall this meeting," Mark said. "Sarah says she came to your office to discuss her concerns," David said. "She says you told her the issue wasn't a priority and that she should focus on the standard test suite." Mark's mind raced. He didn't remember this meeting. But if Sarah said it happened, and his calendar confirmed it... "I don't recall this conversation," Mark said. "But if it's in my calendar, it must have happened." David nodded slowly. "So you're saying you may have had a conversation with Sarah about her concerns, but you don't recall it?" "I'm saying I don't have a specific memory of this conversation. But I'm not denying it happened." David's pen moved. "Sarah says she was concerned enough to schedule a meeting with you. She says she raised the issue directly. And you told her it wasn't a priority." Mark felt the walls closing in. If Sarah's account was true, he had been warned. Twice. And he had done nothing. "I don't recall the conversation," Mark said. "But I take all concerns seriously. If Sarah raised an issue, I would have considered it." "Yet you didn't document any follow-up," David said. "You didn't expand the test suite. You didn't escalate to management." Mark's mouth was dry. "I don't have an explanation." David leaned back in his chair. "Mark, I want to be fair here. I know you've been a good employee. But the evidence is concerning. You were warned about potential issues. You didn't follow up. And now we've had an incident." "I understand," Mark said. "I'm not trying to deflect responsibility. I'm trying to be transparent about what I remember and what I don't." David nodded. "I appreciate that. But I need to be transparent with you too. This is going to HR. They'll conduct a formal review." HR. Mark felt the word like a physical blow. "I understand," Mark said. "One more thing," David said. "I need you to preserve all documentation. Emails, notes, calendar entries. Everything." "I already have," Mark said. "I've been transparent throughout this process." "Good." David stood up. "I'll follow up with HR. They'll be in touch." Mark stood up too. His legs felt unsteady. "David," he said. "I want you to know that I take responsibility for my role in this. I should have followed up on Sarah's concerns. I should have been more thorough." David's expression was unreadable. "I appreciate that, Mark. But right now, I need to focus on the process." The process. Mark knew what that meant. It meant I'm not on your side. --- Mark walked back to his desk. His hands were shaking. He sat down and stared at his screen. His inbox was full of messages—colleagues, vendors, recruiters. But none of them mattered. He opened his calendar and looked at the entry from two months ago. Meeting: Sarah Kim - Code Review Discussion He tried to remember. He closed his eyes and focused. Nothing. He didn't remember the meeting. He didn't remember Sarah coming to his office. He didn't remember telling her the issue wasn't a priority. But if it was in his calendar, it must have happened. She warned me, he thought. And I dismissed her. He opened his email and searched for messages from Sarah. There were dozens. He scrolled through them, looking for any follow-up. Nothing. He had been warned. Twice. And he had done nothing. --- That night, Mark sat at home, staring at his laptop. He had spent hours reviewing his emails, his notes, his calendar. He had found nothing that would help his case. His phone buzzed. A message from Sarah. Mark, I heard you had a meeting with David. I wanted to reach out. I know this is difficult. Best, Sarah Mark stared at the message. He wanted to be angry. He wanted to accuse her of setting him up. But he knew that wouldn't help. He typed a response. Sarah, Thanks for reaching out. I understand you had concerns that I didn't follow up on. I take responsibility for that. I should have listened. Best, Mark He hit send before he could second-guess himself. A few minutes later, Sarah responded. Mark, I didn't want it to come to this. I tried to warn you. I'm sorry. Sarah Mark stared at the message. I didn't want it to come to this. He closed his laptop and sat in the dark. Tomorrow, he would meet with HR. The process would continue. The paper trail would grow. And somewhere, in a notebook or a server, there would be a record of everything he had done wrong. For the record.