She Saved Herself Ten Thousand Times

Chapter 4: The Client's Question

The client review was scheduled for Friday at the Bellwether Harbor Authority offices.

I wasn't sure I'd be allowed to attend. On Thursday, Graham's assistant removed me from the calendar invite. An hour later, compliance added me back as a technical observer. The word observer sat beside my name, as if I had arrived from another company.

I drove to Bellwether before sunrise. The town was an hour and a half from Alder's office, a strip of old brick buildings and newer glass buildings along a wide inlet. The Harbor Authority occupied the second floor of a converted shipping warehouse. I had been there so often that I knew which elevator button needed a second press.

Graham was already in the conference room when I arrived. He stood beside the screen, adjusting the presentation. Devin had arranged paper copies of the launch plan along the table.

"Observer?" Graham asked when I set down my bag.

"Compliance added me."

"I know."

He looked at the stack of papers. My name was not on the title page. His was.

I took a seat near the end of the table.

The Harbor Authority's project manager, Elise Morgan, arrived with two emergency operations staff. Elise was in her early fifties, with a short silver-blond haircut and a canvas folder tucked under her arm. She greeted me with a warm nod before sitting across from Graham.

"Good to see you, Mara," she said.

"Good to see you, too."

Graham opened the meeting. "We're here to confirm the pilot schedule, review the final readiness items, and make sure everyone is aligned for the public demonstration."

Elise glanced at the screen. "The pilot still starts in six weeks?"

"That's the current target," Graham said. "We've resolved the map refresh issue."

Elise turned to me. "Mara, does the latest build show stale data if HarborRoute goes down?"

The room seemed to shrink around the question.

Graham's hand stopped on the clicker.

I looked at Elise. "The patch is in the build. I haven't seen a report from the full failure simulation."

"Why not?" one of the operations staff asked.

"The simulation hasn't been run since the patch was merged."

Graham stepped in. "The code review confirmed the change. We don't consider another full simulation necessary."

Elise's gaze stayed on me. "Was a full simulation part of the acceptance criteria?"

"Yes."

"Can you show me where?"

I opened the project file on my laptop. The signed criteria were in the client workspace. I shared the page on the screen.

Elise read the paragraph in silence. "That's clear," she said.

Graham's voice went harder. "The patch addresses the specific failure. The team believes a full simulation would repeat information we already have."

"Then it should be easy to document that," Elise said.

"We have limited time."

"So do we." She turned to the operations staff. "If a dispatcher sees the wrong road status, we carry the consequences. I need a test report."

Graham folded his hands. "We can arrange one."

"Before the pilot?"

"Before the public launch," he said.

"That isn't what I asked."

I held my breath. The client had made the point I had been trying to make all week, but I wasn't relieved. A client challenge could save the test. It could also give Graham a reason to say I had undermined him.

Elise looked at the launch schedule. "If the test can't be completed in time, we need to discuss the schedule now. We can move the public demonstration. We can't move a storm."

Graham gave her a professional smile. "We understand."

The meeting ended without a final schedule. Elise asked for a written readiness update by Monday, with the test status stated plainly.

In the hallway, Graham waited until Devin was out of earshot.

"You could have said the patch was in the build."

"I did."

"You could have said engineering reviewed it."

"I did."

"You didn't have to emphasize that we hadn't run a simulation."

"That was the question she asked."

"You know she could cancel the pilot."

"She said she could move the public demonstration."

"Same effect on the renewal."

There it was. A real reason, spoken without decoration. The Harbor Authority's renewal was the largest account Alder had won in three years. A successful launch would put Graham's name in front of the board, the investors, and every client Alder hoped to land next. A delayed launch would cost the company money and give his opponents inside the company an opening.

"I know what the renewal is worth," I said. "That's why we can't give them a reason to lose trust."

He shook his head. "Trust isn't a switch we can flip."

"No. It's a thing they can withdraw."

He stared at me for a long moment, then walked away.

On my drive back, I passed the harbor road where the old flood marker stood. The highest line was at my shoulder. I had seen it during our first site visit, when the Harbor Authority staff had taken us through a storage building full of sandbags and battery radios. Elise had told me the water reached that mark during a storm that came through before most of her younger staff were born.

I pulled over in a small public lot and wrote down the next steps before I forgot anything. Not because I thought I could control the result, but because I could control whether I gave the client a straight account of what I knew.

At five, Graham sent the new readiness statement.

The document said that the "HarborRoute display issue had been resolved through code review and validation." It did not say the full failure simulation was pending.

He had added a signature line for me.

I called Anika in compliance.

"Do I have to sign this?" I asked.

"No," she said. "But if you're listed as a contributor, you need to make sure your statement is accurate."

"It isn't."

"Then return it with the correction you believe is necessary. Keep it limited to facts."

I opened the document and changed the sentence to: "The display patch has been merged and reviewed. The full HarborRoute failure simulation has not yet been completed. Acceptance remains pending the test result."

I sent it back to Graham with a note.

I can't approve the original wording. This version distinguishes the code review from the required simulation.

He called within a minute.

"You're making me look like I'm lying."

"I'm making the status accurate."

"I said we'd run the test."

"Then this wording is accurate."

He lowered his voice. "You're still my fiancée."

The word hit harder than it should have. I looked at the ring sitting in the kitchen drawer of my mind, bright and untouched.

"Then don't ask me to sign something I know is false."

He hung up.

I didn't feel brave. I felt hollowed out and very tired.

Before I left work, I sent the corrected statement to the client workspace, as the contract required. My name remained on the page, beside the sentence Graham did not want.