Chapter 36 - THE WOMAN AT THE BUS STOP
Iris Moreno chose the bus stop because, as she said on the phone, a person who had spent years studying transportation routes ought to be able to select a meeting place with decent public access.
Priya and I arrived ten minutes early. The bench stood beside a pharmacy and a diner with steamed-up windows. It was cold enough to make my fingers ache. Iris approached carrying a canvas bag and a folding umbrella. She was in her fifties, with short silver hair and the careful gait of somebody who had spent too many hours behind a desk without remembering to stretch.
“I don't have a secret recording that proves everything,” she said before we sat down.
“That's not what we're asking for,” Priya replied. “We'd like to hear what you personally know and what records might exist. We can explain how your statement would be handled before you decide what to share.”
Iris studied us both. “Good. Because last time I raised a concern, somebody wrote that I was emotional about software. The software didn't get emotional when it was wrong. The families did.”
She ordered coffee at the diner, refused to let me pay, and unfolded a timeline from her bag. She had worked first as a dispatcher, then as a systems analyst for a pilot run by Mercer Data Systems. She knew the difference between the emergency route directory and the live scheduling platform because she had helped design the screen that kept them separate.
“The directory was supposed to be a temporary fallback,” she said. “Imagine a hurricane, a hospital evacuation, a road closure. Authorized staff could confirm a previously consented pickup route when ordinary services were unavailable. It wasn't meant to become a master list of where vulnerable people lived.”
“Did it become one?” I asked.
“I don't know whether every client used it that way. I know the architecture made it possible after a later update. The system started copying historical address fields into an ordinary routing feed. I objected. My supervisor said the synchronization was necessary to keep the service useful.”
She pointed to a date in the timeline. It was three years before the first HarborLine complaints. “This is when I wrote the exception report. I don't have the live system data. I do have my employment correspondence and the report's reference number, which I retained under an agreement. My lawyer has reviewed what I can lawfully disclose.”
Priya asked whether Iris would authorize contact with her attorney. She agreed. She did not consent to us publishing her name or using her photograph, and we recorded that preference. Her testimony was potentially important, but it belonged to her until the proper processes required otherwise.
“What happened after you objected?” I asked.
“They told me the project would be canceled and the data returned. Then a new manager offered me a position at Northstar Continuity Services. I turned it down. A colleague took it and called me six months later to complain about undocumented imports. I didn't hear from her after that.”
“Do you remember her name?”
“Ruth Ellison. Not to be confused with the archivist you know. She was brilliant with legacy systems and terrible at office politics.”
I wrote the name down. “Is she still working there?”
“I don't know. I won't pretend she is or that she's involved in anything wrong. All I can tell you is where we worked and what she said at the time.”
The waitress brought food Iris insisted we order, because she said she trusted people better when they weren't hunched over an empty coffee cup. We ate grilled cheese sandwiches while Priya explained how the next steps would work. Iris listened closely. She wanted her report preserved, not turned into a dramatic clip for a documentary.
After lunch, she led us to the bus stop again and gestured toward an advertisement on the shelter. “Do you see that QR code? It offers real-time arrivals. Useful, if it works. But somebody has to decide where the information comes from and what happens when it's wrong. Technology never lets you escape responsibility. It just makes responsibility easier to misplace.”
Her words stayed with me as I returned to Blue Harbor. We had spent months establishing manual confirmation procedures, and it was tempting to believe the old vulnerabilities were safely behind us. Iris had described a different kind of risk: a system that remained quietly connected after the project meant to authorize it had ended.
Celeste called an emergency operational review, and the independent technical assessor explained what could be tested without exposing the private data to yet another set of strangers. They would analyze logs, permissions, and field mappings in a controlled environment. They would use anonymized test records where possible. A real person's address would not become a prop in a software demonstration.
At the meeting, Nia Phillips described how the routing screen had displayed Leah's old address as if it had just been confirmed. “The screen didn't warn me it was historical,” she said. “If I hadn't called, the driver would have gone there. Maybe nobody would have noticed until the child missed the appointment.”
The assessor nodded. “That's the difference between having a record and having a trustworthy record. We're going to examine not only who imported it, but how the software presented its certainty.”
When the meeting ended, Nia lingered beside me. “I've been thinking about my supervisor,” she said. “He supported me when I refused to delete my notes. I didn't expect that. I think I judged him unfairly because other people had dismissed me.”
“You can thank him,” I said. “And you can still expect him to keep supporting accurate records.”
She smiled. “Both things can be true.”
Nia later sent a short message to the routing training coordinator, with her supervisor copied. She proposed that screens distinguish three different things: an address confirmed directly by a family, an address copied from an external source, and an address still awaiting verification. The suggestion seemed obvious once she wrote it down. It had somehow survived years of software design without being implemented. The coordinator invited Nia to take part in a test session and agreed that front-line staff should be compensated for their time. I liked the compensation detail. Too often the people who discovered the flaws were expected to donate their labor to repairing them.
On Saturday Enzo and I took Amelia to the small science museum she'd been begging to visit. She spent forty minutes at an exhibit about load-bearing structures. Enzo tried to build a bridge with a hundred plastic blocks and failed. Amelia assembled one from thirty-two and looked at him with devastating pity.
“More isn't always stronger, Dad.”
“I'm learning that.”
At lunch she asked why I seemed distracted. I told her I was thinking about a work problem, and she accepted that without asking for details. Children deserve adults who can answer honestly without handing them every burden.
Later Enzo and I walked along the river while Amelia explored a supervised exhibit with June. He told me his lawyers had found records showing that his former company had paid Mercer for an initial feasibility study. The study recommended strict separation between historical records and live routing. It also listed unresolved questions about deletion and permission revocation.
“Did your committee read those recommendations?” I asked.
“We received the summary. I can't prove who read every page. I know I didn't follow up when the pilot was abandoned. I'm going to say so in my statement.”
“Are you afraid?”
“Of what it might reveal, yes. Of being seen as responsible for more than I knew, yes. But I think I'm more afraid of being the man who calls that uncertainty an excuse not to cooperate.”
I slipped my hand through his. “You can't revise the past by pretending you were wiser.”
“No. Only by helping make the present more accountable.”
By Monday Iris's attorney had authorized her exception report to be provided to the independent review team. The final page contained a note she had written after a meeting with senior managers: NO CUSTOMER SHALL BE ROUTED BY UNVERIFIED HISTORICAL LOCATION. The date was clear. So were the names of attendees, though we did not know who had accepted or rejected her recommendation.
The assessor compared the report number with a record from the current vendor. A migration file existed with the same identifier, but its creator field had been replaced during a software conversion. The missing attribution meant the team could not yet identify who had activated the import. It did not mean the action had been invisible forever.
May you like
That night I sat at my desk with the incident timeline arranged in three columns: what we knew, what people had told us, and what remained unverified. In the third column I wrote a new question: WHO BENEFITED FROM KEEPING THE HISTORICAL FEED ALIVE?
Then I crossed out BENEFITED and replaced it with WHO REQUESTED, APPROVED, OR FAILED TO STOP IT? The first question invited me to invent a motive. The second offered something we could actually investigate. Outside my window, a bus passed beneath the streetlight and stopped exactly where its passengers expected. I watched a woman step down carefully, take a child's hand, and cross the street. Nobody applauded. The route worked. That was what we were trying to protect.
