Chapter 4 - The Reading That Should Have Triggered an Alarm
On Monday morning, I stood in a municipal conference room overlooking a gray stretch of the Chicago River and held a small sensor in the palm of my hand. It looked harmless: a metal cylinder, a black cable, a printed serial number. The panel chair, a retired engineer named Marianne Cole, asked me to explain what it was supposed to do.
"It warns operators when a solvent concentration reaches a threshold that requires action," I said. "It isn't an ornament. People rely on the warning to know when to stop a process and investigate."
There were no television cameras inside. Cass sat behind me. Representatives from the city, the company, and a workers' organization had seats around the table. I had insisted on the session being independently recorded so no one could later quote half a sentence as my complete conclusion.
I described the defect with the care I'd used in laboratories: under a particular sequence of restarts, an adjustment in the software could display readings lower than the raw instrument data. I had observed it in early tests, documented it, and requested field confirmation. I did not claim every installation was affected. I did not claim injuries I couldn't establish. That was why I had come: uncertainty was a reason to check, not a reason to celebrate the launch schedule.
A company lawyer stood. "Mrs. Vance, weren't you paid under a separation agreement?"
"My employment agreement addressed my compensation. It didn't change how a sensor behaves."
"Your personal relationship with our chief executive ended badly."
"It did. If you have a technical question, please ask it."
Marianne intervened before the lawyer could turn my marriage into a second hearing. She asked for the test number. I gave it: EV-17. A company engineer searched his tablet and said the record had been designated a duplicate. He couldn't find its original data attachment.
"I have the attachment," I said. "I preserved the copy I was authorized to keep as the originating researcher. I supplied it to the panel last week."
I projected two graphs. The first showed raw readings climbing during a controlled simulation. The second showed the displayed values remaining nearly flat. For a full thirty seconds the room was silent. Then Rosa Alvarez, a maintenance supervisor invited by the workers' organization, leaned toward her microphone.
"That's what I've been trying to describe," she said. "Our technicians saw numbers that didn't match the independent handheld instrument. Management told us the handheld units were old."
"Do you have a log?" Marianne asked.
"I do. My supervisor told me to stop keeping a separate notebook, so I filed a maintenance report through the standard system. I brought its reference number."
The company engineer asked for a pause. Cass touched my elbow and whispered, "Breathe. Your part is clear."
Across the room, Julian entered through a rear door. He hadn't announced himself. He took a chair against the wall rather than joining the company's table. He listened while Rosa described the date, location, and readings. When the lawyer tried to interrupt her, Julian said, "Let her finish."
That was a small sentence. It was also the sort of sentence I'd waited years to hear from him.
At lunch, Marianne called a recess so the panel could request the original version history and maintenance logs. Cass and I ate sandwiches on a bench beside the building. My phone showed three photos from Tessa: the girls making a cardboard train, Emma wearing a conductor's hat, Sophie holding a sign that said NO TICKETS REQUIRED. I sent back a picture of my sandwich and told them I was coming home for dinner.
Julian approached alone, stopping far enough away that I could choose whether to speak. "I looked at the graphs," he said.
"Good."
"Lena told me the revision was cosmetic. She said your concern had been tested and closed."
"The original closeout required field measurements. Are those in the archive?"
"I haven't found them. I've asked the board's audit committee to bring in an independent reviewer. I'm suspending deployment of that revision until they can account for the data."
I didn't thank him. I did say, "That gives the technicians a chance to check their instruments before anything else goes wrong."
He looked out at the river. "Five years ago I took her account of your work because it was easier than talking to you. I did the same thing at home."
"Then don't do it again," I said.
We were interrupted by a call from Cass's office. A reporter had received a package claiming I was using undisclosed children to extort the founder of Vance Energy. It included a photograph from the airport and part of a court filing from our divorce. The children weren't named, but the accompanying note listed their ages and described our neighborhood. The reporter had called Cass for comment rather than publishing it outright.
"Who sent the package?" Julian asked.
"The reporter won't identify the source," Cass said on speaker. "But the attachment includes internal company language. We're preserving everything and requesting the children's details not be published."
Julian looked shaken. "I'll tell our communications team to—"
"No," I said. "Your communications team helped bring a photographer to that airport. Let your independent lawyer handle preservation. Cass will handle the reporter."
He nodded slowly. "You're right."
Inside, the panel reconvened. Marianne announced that the company had agreed to pause use of the disputed software revision while the independent technical review continued. Rosa exhaled so sharply I could hear it across the room.
When I arrived home, the girls met me at the door with their cardboard train. Emma insisted I sit inside it even though my knees were too high. For twenty minutes I was the passenger on a journey to the moon. Then Sophie climbed beside me and whispered, "Did the man from the airport call you?"
"He did. We talked."
"Did he say sorry?"
"Yes."
"Did that fix it?"
I touched the cardboard window she had cut with safety scissors. "Not by itself. But it was a beginning."
May you like
Before bed, the independent panel sent a request to preserve the entire software version history, including the names of everyone who authorized its release. Julian's name appeared on the last approval page. His signature wasn't forged. He'd approved a system he hadn't understood well enough to question.
I sat with that document for a long time. There was no villain convenient enough to carry every ounce of responsibility. Julian would have to tell the truth about his own part, even if it cost him the company he had built.
