Chapter 7: A Paper Trail
The morning after we sat around my kitchen table, I woke to a phone full of notifications and no clear answer about what I was supposed to do with any of them.
The graduation video was still being passed around. I knew that from the messages people had sent me, not from any reliable count of how many people had seen it. One version showed Vanessa tearing the letter. Another started with the CEO entering, making it look as if Meridian had appeared to rescue my future. The cut between those moments did a lot of work.
I didn’t watch either version again.
Instead, I opened the email Meridian had sent the night before. My scheduled call with the recruiter was still on the calendar. The subject line was plain: Follow-up on graduation video.
I had expected the meeting to be about damage control. I hadn’t expected how much I wanted a document that said, in ordinary, unexciting words, that my job was still mine.
The recruiter joined the call a few minutes after I did. She had the same composed manner she’d had during the hiring process—not cold, exactly, but careful about distinguishing what she knew from what she didn’t.
“Before we talk about the video,” she said, “I want to answer the question that’s probably been sitting in the back of your mind. Your employment agreement is active. Your position and salary are unchanged.”
I let my breath out slowly.
“Senior systems,” I said. “One hundred twenty thousand a year.”
“Correct. That’s what you signed, and that’s what we have on file.”
“Is there anything about the video that could affect my start date?”
“No.”
Her answer came without a pause, and I appreciated that more than I would have appreciated a speech about how sorry she was.
“Your hiring decision was made through the normal process,” she continued. “The ceremony didn’t create the offer, and the video doesn’t undo it. I can send you a written confirmation of your role, salary, and start-date logistics for your records.”
“Yes, please. I want the record to be clear.”
“It should be.”
She shared her screen. The employment system showed my signed agreement, dated two days before graduation. The ceremonial letter Vanessa had torn wasn’t listed anywhere. It had never been the thing holding my future together.
Seeing the electronic record steadied me. Not because I’d seriously believed the scraps on the ballroom floor could cancel a contract, but because there was something different about watching a stranger confirm, in the ordinary course of business, that the choice I’d made was real.
The offer hadn’t come from the CEO’s entrance. It hadn’t come from a crowd’s sympathy. It had come from the work I’d done and a company that had decided to hire me.
“Thanks,” I said.
The recruiter nodded. “Now, about the video. We’ve seen versions circulating, including one that suggests the CEO’s announcement was connected to your employment. We’re not going to repost it or use the family situation in any recruiting or marketing material.”
I’d known that was the answer I wanted. Hearing it still made my shoulders loosen.
“Could Meridian issue a statement correcting the part about the job?”
“We can correct inaccurate business information if it starts affecting the company or your employment. But we don’t want to amplify a personal conflict just because it’s drawing attention.”
“That’s what I want too,” I said. “I don’t want my family turned into a story the company tells to make itself look good. And I don’t want anyone thinking I got my job because a camera happened to be pointed at me.”
“We agree. Your employment stands on its own. The project discussion stands on its own too.”
There it was: the other piece of the meeting I’d been dreading.
“So the pilot proposal is still just a proposal?”
“Yes. The review is internal. You haven’t agreed to project work, and nothing is approved for testing or deployment. We’ll send the draft materials when they’re ready, and you can decide whether you want to review them.”
I kept my hands folded on the desk so I wouldn’t pick at my thumbnail.
“Then I want the boundaries documented too. I’m willing to review the proposal on its merits. I’m not agreeing to do extra work because of the video, and I don’t want my family’s actions included in a presentation about the prototype.”
“Understood,” she said. “I’ll make sure that distinction is reflected in the follow-up.”
“Also, if someone asks about the video?”
“You don’t have to comment. If a question concerns your job, you can refer them to our confirmation. If anyone contacts you on behalf of Meridian, we’ll coordinate first.”
Her care with the language mattered. She didn’t promise that the internet would stop watching, or that a clip couldn’t distort what had happened. She offered a line between what the company needed to address and what belonged to me.
The call lasted less than half an hour. When it ended, I stayed seated, looking at the blank screen. My mother’s invitation to meet that weekend was still unanswered. The recruiter hadn’t asked about my family. I hadn’t offered an explanation.
For once, a conversation about my life had been allowed to stay about my life.
A few minutes later, two emails arrived. The first confirmed my employment terms and said my start-date logistics remained as written in the signed agreement. I saved it to my records folder, then saved a second copy somewhere I could find it without searching. It was a small act, but I wanted a paper trail that didn’t depend on anyone’s memory or mood.
The second email concerned Meridian’s project review. It had been forwarded by the project coordinator, with a note that the internal reviewers were continuing to examine the prototype’s limitations. I opened the attached comments.
Most were questions I expected: what happened if a record was outdated, how a user would know when the system couldn’t verify something, whether the display made its limits clear. I had already put warnings and timestamps into the design because a tool that appeared more certain than it was could do harm.
Then I reached a comment near the bottom of the page.
Failure case not addressed: If an interrupted synchronization leaves part of a patient record unavailable, how does the interface distinguish missing information from a confirmed blank field? In particular, could a user mistake an absent allergy section for confirmation that no allergies are recorded?
I read it once.
Then again.
The prototype was read-only. It didn’t make treatment decisions or replace the clinic’s existing system. That was part of the point. But “read-only” didn’t make an ambiguous screen harmless. If a clinician saw an empty space and understood it as a reassuring answer, the system could mislead without ever changing a record.
I pulled the current interface onto my laptop and found the allergy section. In the synthetic records I’d used, the field was either populated or clearly marked. I had tested a network outage. I had not tested an outage in the middle of synchronization, with some information present and some missing.
The reviewer wasn’t claiming that the problem had happened. They were asking whether I knew what the system would do if it did.
May you like
I placed my hands on the keyboard and opened a new test plan. At the top, I typed the case exactly as they had described it.
Then my cursor blinked beside the word Expected. I had no safe answer to put there yet.
