Chapter 4: Terms of the Pilot
The next morning, I read Meridian’s calendar invitation twice before joining the call.
The title was still plain: Meridian Dynamics — Claire Bennett — Morning Call. No mention of the video, no mention of my sister, no hint that my life had become a tidy little story strangers could edit to fit a caption.
I sat at my kitchen table with a mug of coffee going cold beside me. My graduation cap rested on the counter. I hadn’t decided whether to put it away or leave it there as a reminder that the day had been mine, too.
A woman from recruiting joined first, followed by someone from Meridian’s communications team. They congratulated me again, then got straight to the point.
“We want to make sure you’re comfortable with how we handle questions,” the communications lead said. “We’re not planning to comment on a family matter. We also don’t want your employment announcement tangled up with the video.”
“Good,” I said. “I don’t want the company making a statement about my family.”
“Of course. If anyone contacts you claiming to speak for Meridian, please let us know. And you don’t need to respond to people who message you about the clip.”
I glanced at my phone, face down on the table. Overnight, the video had kept moving. I knew that because my friends had been kind enough to tell me, then had apologized for telling me.
“Some versions say your CEO arrived and saved my job,” I said. “That’s not what happened.”
“We understand,” the recruiter replied. “Your agreement was signed before graduation. The company will not suggest otherwise.”
For the first time since the clip began circulating, I felt my shoulders loosen a little.
The communications lead explained that Meridian wouldn’t repost the video or use it in a company announcement. If reporters or strangers asked about it, I could direct them to recruiting or say nothing. They weren’t asking me to defend myself, and they weren’t asking me to perform gratitude for a job I’d already earned.
“Is there anything else you’d like clarified?” the recruiter asked.
I thought about the edits: the cut where the CEO entered, the swelling music, the caption describing a rescue. Then I thought about all the versions of my family life that had never been filmed.
“No,” I said. “I understand what you’re asking.”
The communications lead left the call. The recruiter stayed on.
“There’s a separate discussion about the proposal Mercer mentioned at graduation,” she said. “The project team has a scope briefing this morning. It’s optional, and it isn’t connected to your employment agreement. Would you like to join?”
I looked down at the notes I’d scribbled beside my coffee: What exactly is being proposed? What would they expect from me? What happens if it doesn’t work?
“Yes,” I said. “But I want to be clear that I’m not agreeing to anything today.”
“Absolutely. I’ll send the link. You can listen and ask questions.”
The second call began ten minutes later. David Mercer was there, along with two engineers and a project coordinator I hadn’t met. One engineer shared a diagram that looked familiar from the prototype I’d built for my senior design project: a small system meant to help clinic staff access essential records when their network went down.
Seeing it on a Meridian slide made my stomach tighten. It was still my work, but on the screen it looked more official than it had in my apartment, where I’d tested it between laundry and late-night assignments.
Mercer spoke first.
“This is a discussion of a possible paid evaluation,” he said. “Nothing has been approved for deployment. We’re here to define what we’d need to learn and what limits would make the evaluation responsible.”
I appreciated that he didn’t lead with praise. Praise could make a person feel they owed someone an answer.
One of the engineers outlined the prototype’s promise: in a network outage, authorized clinic staff might be able to access a limited set of essential records from a local system. But he also named the obvious risk. A record saved before an outage might be out of date by the time someone needed it.
“If the system comes back online and there are conflicting updates,” I said, “we need to know exactly what happens. It can’t quietly choose which version to keep.”
“Agreed,” the engineer said. “Conflict handling is one of the areas we’d evaluate.”
“What data would be used?”
“Initially, synthetic records,” the project coordinator said. “If the design review supports moving forward, any later testing would require separate approvals and a defined environment. That isn’t what we’re deciding today.”
I wrote that down.
The engineer described another concern: access controls. If the local system stayed available during an outage, the team would need to verify that people could see only what their role permitted, even when the usual network checks weren’t available.
“And what does ‘available’ mean in this proposal?” I asked. “Are you measuring whether a record can be retrieved, or whether it can safely be used?”
The engineer paused, then nodded.
“That’s a fair distinction.”
I felt a small, familiar spark of satisfaction—not because I’d caught anyone out, but because they were treating the question as part of the work instead of as a challenge to their authority.
I suggested that an initial evaluation stay read-only and use synthetic records. Every displayed record should carry a clear timestamp and a warning that it might be stale. If a record’s integrity couldn’t be verified, the system should show that it was unavailable rather than offer a confident-looking answer.
“No write-back?” one engineer asked.
“Not in the initial evaluation,” I said. “And no one should use the prototype as a substitute for the clinic’s normal records or procedures. The team needs a way to stop the test immediately if it behaves unpredictably.”
The project coordinator added the points to a shared document. No one said my suggestions solved the larger problems. They didn’t. I had designed a prototype, not a finished system, and clinic records weren’t a place to confuse promising with safe.
“What would count as success?” I asked.
The engineers began listing measures: access time, availability during a simulated outage, accurate permissions, and how the system behaved when the network returned. I asked them to include failure cases, not just the situations in which everything worked.
“If we only measure the clean run,” I said, “we’ll learn that it works when nothing goes wrong.”
One of them smiled.
“That’s why you’re here.”
I didn’t let the compliment rush me.
“How much time are you expecting from me?”
“We don’t have a final estimate,” the coordinator said. “We’d need to define the evaluation before we could make one.”
“That needs to be in writing,” I said. “I’m starting a full-time job. I can’t promise open-ended hours on top of it.”
“Nor should you,” Mercer said. “Your position is unchanged and stands on its own. This proposal is separate, and you’re free to decline it.”
He said it as plainly as he had onstage. This time, though, there was no ballroom listening and no clapping to blur the meaning. It was a boundary drawn in ordinary language.
The engineer asked whether I could send them the test cases I’d used in my senior project.
“I can review what’s appropriate to share,” I said. “But I’d want the scope, compensation, hours, and ownership terms before I do project work.”
“Reasonable,” Mercer replied.
He didn’t promise a title, a fast-track promotion, or a future announcement. He didn’t tell me the project would transform health care. He asked whether I was still interested in reviewing the proposal once the team put the terms on paper.
Interested was not the same as committed. I had spent years learning that precision mattered, even when the words were less dramatic.
“I’m interested in reviewing the documents,” I said. “That’s all I can agree to today.”
“Then that’s all we’ll ask,” he said.
After the call, the project coordinator sent a note confirming that the scope and compensation documents would follow. The message described them as drafts for review, not a contract or approval to begin. I saved it in a folder beside my signed employment agreement.
For a few minutes, I sat at the table without opening anything else.
I thought about the questions the engineers had asked, the ones they hadn’t answered yet, and the work still needed before anyone could call the prototype reliable. Then I put the torn piece of the ceremonial offer letter—the one I’d slipped into my pocket at the ceremony—on the table beside my coffee.
Its jagged edge caught the light.
The paper had been damaged. My agreement had not. The pilot was only a possibility. My job was real. None of those facts required me to pretend yesterday hadn’t hurt.
By the time I reached my apartment, the day had warmed the hallway. I unlocked the door and saw someone sitting on the floor beside it, arms folded around her knees.
Vanessa looked up.
For one quiet second, neither of us moved.
Then she stood.
“I know you said you didn’t want to talk in public,” she said. Her voice was lower than it had been in the ballroom. “So I waited here.”
I kept one hand on my keys.
“That doesn’t mean I’m ready to talk.”
May you like
“I know,” she said.
But she hadn’t left.
