Chapter 32 - THE ADDRESS THAT MOVED
On Wednesday morning Leah discovered that somebody had moved her home without moving a single piece of furniture.
She phoned just after eight, when I was halfway through a bowl of oatmeal in the Blue Harbor staff kitchen. “The transportation service has a different address for us,” she said. “The driver called from a building three blocks away. His screen said Jonah lives there now.”
I put down the spoon. “Did Jonah get into the vehicle?”
“No. I canceled the ride. I wasn't going to send him anywhere while the records were wrong.”
“You made a careful choice. Can you stay home today, or do you need another way to get to the appointment?”
“His appointment is important, but we can reschedule. He's worried it's his fault. He thinks he said the wrong thing to somebody.”
The old transport scandal had taught Jonah to ask who was driving, where he was going, and whether the route had been confirmed. Those questions were no longer merely the habits of a frightened child. They were reasonable safeguards. But a wrong address could turn the very safeguards into something that felt like an accusation. I hated that.
Celeste and I checked the family's file through the access channel assigned to my team. The current address was correct in Blue Harbor's own database. The external provider's system showed a change entered at 2:14 the previous afternoon, with a reference that identified a routine overnight synchronization. No named staff member had approved it. The change was labeled AUTOMATED HOUSEHOLD LOCATION UPDATE.
Celeste stared at the screen. “We stopped allowing that kind of update last year.”
“In our system,” I said. “Maybe not theirs.”
She asked the privacy officer to suspend automated transfers for the affected records while she contacted the independent provider. She did not make a blanket claim that somebody had hacked the database. The wrong address might have come from a bad cross-reference, stale imported data, or malicious interference. Each possibility required a different response, and all of them could harm a child.
At eleven, a young dispatcher named Nia Phillips arrived in the conference room with an exhausted face and a folder full of handwritten notes. She worked for the independent transportation company, not HarborLine, and she had been the one to call Leah. Her supervisor had told her to refer all questions upward. Instead she had asked for permission to correct the immediate problem in person.
“I don't want to lose my job,” she said before sitting down.
“We don't want you to,” Celeste replied. “You're here as someone with direct knowledge of a route discrepancy. We'll document what you know and who has authority to investigate.”
Nia showed us the screen prints she'd saved with her supervisor's knowledge. The altered address belonged to a vacant house, one that had been listed on a demolition permit two months earlier. The route engine treated it as a valid destination because the address fields matched a historic emergency registry. The software had not invented a random location. It had revived an obsolete record and described it as current.
“Did you notice any other changes?” I asked.
“Four in the last ten days. Two were medical pickups. One was a return trip for a woman who no longer uses the program. I corrected those after calling the families. But today's change looked more serious because it had a child's name.”
“Have you reported the pattern?”
“Yes. I sent it to the vendor help desk and copied my supervisor. They told me the nightly update was probably normal.”
Celeste took a breath. “A correction that wasn't authorized isn't normal. Thank you for keeping records.”
After Nia left, Priya joined us by video. She reminded us not to use Leah's case to pull a broad search of private addresses without a defined purpose and authorized review. It was exactly the kind of boundary I might once have resented when I was frightened. Now I was relieved somebody was drawing it.
We drafted individual notifications to people whose records had been confirmed affected, explained the scope of the discrepancy in plain language, and offered independent assistance with appointments. The notices did not display addresses in the subject line. They did not force recipients to call the very vendor whose information was being questioned. That detail had been suggested by Leah during an earlier advisory meeting. Her advice mattered now.
Late that afternoon, I went to her apartment at her invitation. Tessa was at a friend's house. Jonah sat on the carpet beside an unfinished model of the moon, carefully attaching foil to a cardboard crater. He looked up when I entered and asked whether I was from the safety committee.
“Not exactly,” I said. “Your mom invited me because there was a mistake in a travel record.”
He frowned. “Did I say we moved?”
“No. You didn't cause it. Adults are checking where the information came from.”
“Will the next driver know?”
“We're going to confirm the pickup details with your mom before the next trip. You can ask her to show you the confirmation if that would help.”
He considered that, then returned to his moon. “I want it to look like the real moon. Not the pie.”
“The pie was memorable,” I said.
“That's why this one has to be scientifically correct.”
Leah led me to the kitchen where she had made tea neither of us particularly wanted. She lowered her voice. “I nearly called my landlord and asked to leave. It brought everything back. Then I remembered what you told me at the gate: I get to choose what help I want.”
“You do.”
“So I want somebody to tell the truth about how this happened. Not publish my children's names. Not put us on television. Just fix the system and tell people.”
I promised only what I could: that we would pursue the discrepancy through the established response, share verified findings with those affected, and challenge any effort to hide behind the word technical. She nodded. Then she asked whether I wanted to see Tessa's latest painting of the blue gate. I did. It showed Jonah's red rocket brighter than real life, with the bell rope hanging down like a line somebody could grasp.
That evening Enzo came to my apartment with bread and a stack of old committee minutes he had given his legal team to review. He asked whether he could summarize what he remembered without bringing confidential material into my home. I told him yes, as long as we kept the investigation with the right people.
“Five years ago a county consortium explored something called the Common Route Exchange,” he said. “It was supposed to let different authorized providers confirm emergency routes when families changed services. My old transport holding company considered licensing software from a firm called Mercer Data Systems. I voted to fund a feasibility study.”
“Was Sofia involved?”
“She objected to the idea before there was even a pilot. She wrote that a shared directory might become a permanent shadow file. I remember that phrase because I thought it was dramatic.”
“And now?”
“Now I think she understood something I didn't.”
I watched him take that admission seriously, not as a gesture intended to win approval. “Do you know whether they built the exchange?”
“No. I left the procurement subcommittee before the final contract. My lawyers are requesting the records through the appropriate channels. I won't pretend a feasibility vote had no consequences.”
The name Mercer sounded familiar. It appeared in the 2019 county transport review, attached to a technical consultant, not as a finding of misconduct. I wrote it down on the incident timeline, clearly labeled as a possible connection rather than proof.
On Friday, Nia called again, this time through the formal reporting channel. She had received an instruction from the routing vendor to delete her manual notes because they might confuse the audit trail. Her supervisor had refused and asked for the instruction in writing. Nia sounded almost disbelieving when she told me.
“My supervisor actually said no,” she said. “I thought they'd tell us to keep quiet.”
“Sometimes procedures work because someone chooses to use them.”
She laughed nervously. “It's a strange feeling.”
Before we ended the call, she added that an older import record had surfaced in the vendor's log. Its source label was not HarborLine. It was COMMUNITY EMERGENCY ROUTES — REVISION C. The exact title printed on the binder photographed in the anonymous envelope.
May you like
I stood by the window while the city turned gold beneath a low winter sun. The data in a forgotten binder was still influencing the route of a living child. That was not a ghost story. It was a recordkeeping failure with a human face, and somewhere behind it were decisions people had made about what deserved to be kept and who should be allowed to use it.
I thought of Sofia, who had argued that helping people should not require collecting more about them than they agreed to share. I wished she could tell us where she'd been overruled. But even if she could, our responsibility would be the same: find the copies, protect the families, and make a system that listened when someone said the address was wrong.
