Chapter 42 - THE TWENTY-THREE SILENT PHONES
There were twenty-three households in the first confirmed group, and I hated how quickly the number became a headline.
It appeared in an email before we'd reached everybody on the list. It appeared in a councilmember's question before the verification calls were finished. By lunchtime, someone had written that twenty-three vulnerable families had been "abandoned by the city," which might make people click a link but did nothing to explain what had actually happened.
We knew that twenty-three test records required review. We did not yet know whether every corresponding household had missed the alert. Some people had multiple methods. Some addresses belonged to vacant units. A few residents had changed their contact preferences since the data had been exported. There could be more failures elsewhere. Accuracy wasn't an excuse to minimize the problem. It was the first thing we owed the people affected.
Carmen and I set up a supervised contact process with the privacy officer. We used the channels residents had previously authorized, made each conversation optional, and asked only the questions needed to determine whether the test alert had reached them. The calls were slow. Nobody had to explain a medical condition to prove that their phone should ring.
Mrs. Delaney volunteered to attend a public feedback session and began by reminding us that she was not a substitute for every older resident in Port Ellery.
"You can ask me what I think," she said. "You can't say 'we asked the elderly' and point at me."
"We wouldn't," I replied.
"Good. Because my opinions change before lunch."
Mr. Hsu came with his wife, who had received an alert by email after the test was over but not the landline call she'd requested. He held a folded bus timetable in his pocket and explained why he didn't carry a smartphone.
"I don't need a lecture about new technology," he said. "I need to know whether someone will knock when the river rises."
"The current plan includes a staffed backup process," I told him. "We're verifying where it failed in the drill."
"Then put the plan on paper, too."
We did. Carmen arranged a plain-language printed notice explaining the test limitation, the routes available now, and how to request a correction. A translator reviewed the versions in the neighborhood's three most-used languages. We posted them at the market, library, clinic, and community center, after checking that the notices would not be mistaken for an active evacuation order.
The next complication arrived in the form of a lawyer's letter from Northstar Civic Systems. The company disputed our use of the phrase "unconfirmed delivery" in a training note and requested that all staff refrain from discussing the platform's performance pending its internal assessment.
Elaine read the letter with the expression she reserved for badly designed forms. She was planning to reduce her hours next year, but retirement hadn't made her easier to intimidate.
"They can dispute our technical conclusions," she said. "They don't get to tell a public office not to record what residents reported."
"Our legal team will respond," Carmen said.
"They should. And nobody should forward the letter to social media in a fit of righteous anger."
I put down my phone. Elaine looked straight at me.
"I hadn't done anything," I said.
"I know. You're my favorite person to warn before she does."
That evening Alessandro came to my apartment, where Lily was making paper leaves for the neighborhood dinner. He carried a bag of tomatoes and a bottle of sparkling cider. He watched me sort documents at the kitchen table until I closed the folder.
"Can you tell me what's happening?" he asked.
"Some of it. Not the individual records."
"I don't want the records."
That was the right answer. We made pasta while Lily insisted that every leaf needed its own personality. My mother dropped by with a pot of soup she said she'd made "accidentally," which was how she described cooking enough to feed an entire block. We talked about school, the market, and the upcoming holiday until Lily went to bed.
Afterward, Alessandro sat across from me in the quiet kitchen. "I have something to disclose," he said.
A peculiar coldness settled in my stomach. We'd learned not to save difficult conversations for the moment when they could do the most damage, but that didn't mean I enjoyed hearing the words.
"Go ahead."
"My family's charitable investment office participated in a diversified infrastructure fund several years ago. The manager sent a routine portfolio update today. One of the fund's smaller holdings is connected to Northstar's parent company."
I looked at him. "Did you know that at the council presentation?"
"No. I requested the underlying list as soon as I recognized the name. I haven't had any role in the contract, and I won't contact the city on their behalf. I've asked independent counsel to review what, if anything, requires disclosure from me."
"How small is small?"
"Less than one percent of that fund's assets, according to the preliminary statement. I want to verify it before repeating a figure publicly."
I appreciated that he hadn't tried to bury the connection under a reassuring adjective. Still, it was difficult not to hear the echo of old waterfront contracts, old influence, old claims that one powerful man couldn't possibly know what every person working under him had done.
"I need some space to think about this," I said.
"Of course."
"It doesn't mean I'm angry with you."
"You may be when you've thought. That would be fair too."
He left after washing the dishes, without asking me to promise that the disclosure changed nothing.
I sat at the table and looked around the apartment I'd built a life in. Lily's drawing was taped beside the refrigerator. My mother's soup was cooling on the stove. Through the window, someone was walking a dog beneath a streetlight that finally worked. I was grateful that Alessandro had told me. I was also tired of the way complicated money could enter a room even when nobody had invited it.
The next morning Northstar's communications director, Mara Sloane, called about the photograph of Lily. She sounded friendly, experienced, and precisely prepared.
"We sourced the image from a publicly shared community-event album," she said. "Our team understood it to be available for civic education."
"Publicly visible doesn't mean available for a private sales presentation," I replied. "Who took it, and who gave permission for my daughter's image to be used?"
"We're investigating that."
"Please stop using the photograph while you investigate and confirm in writing where it has appeared."
"We can remove it from future presentations."
"I'm also asking what you've already distributed."
There was a small pause. "I'll come back to you."
I told her I was speaking as Lily's parent about the photograph, not as a city representative about the contract. The distinction mattered. I wanted it written down before somebody tried to turn my daughter's privacy into a public bargaining chip.
At work we received a technical note from the city's independent testing consultant, Samira Ortiz. She had compared the high-level system configuration with the approved enrollment standards. Her preliminary finding was narrow but serious: the test had treated alternative-contact enrollments as successfully transferred to a separate module without confirming that module had executed the notifications.
"It's the electronic equivalent of moving a stack of letters into a different tray and recording them as delivered," Samira explained on a call.
"Could that happen by mistake?" Carmen asked.
"Absolutely. It could also persist because nobody tested the end-to-end process. We need change logs before drawing conclusions about why."
"Who has those logs?"
"The vendor and the city integration team. The city's records officer has issued a preservation instruction."
That afternoon the verified contact results came back. Eleven households confirmed they hadn't received the test by their preferred method. Five had received a secondary notice. Four were still unreachable through permitted channels. Three records were duplicates or outdated and needed correction. We published the category totals with an explanation that verification was ongoing. Nobody was described as harmed by a drill simply because a message hadn't reached them. Nobody was told the problem was harmless either.
On Friday, Priya asked me to meet her at the new market. A vendor named Rose had received a call from someone claiming to be from the city. The caller knew she'd requested an accessible evacuation route and offered a "premium priority account" for a monthly fee. Rose hadn't signed up. She'd hung up and reported it.
"Could it be a scammer using public information?" Priya asked.
"It could. We'll send the details to the appropriate team and warn residents without repeating information we shouldn't expose."
"The caller knew her new phone number," Priya said. "She updated it after the river drill."
I felt the temperature of the room change, though nothing physical had happened. We didn't know where the number had come from. But the timing raised a question we couldn't leave unanswered.
That evening, I walked with Lily past the restored gate. She rang her bicycle bell at two children playing near the path. Alessandro wasn't with us. We had agreed to spend the weekend separately while I considered what boundaries were needed around his family's investments.
"Are you sad?" Lily asked suddenly.
"A little worried about grown-up work."
"Did you do something wrong?"
"Not that I know of. Sometimes something goes wrong even when people try hard. Then we find out what happened."
She considered this, then held out her hand. "We can still have dinner with everybody, right?"
"Yes," I said. "We can."
My phone vibrated as we reached the apartment stairs. It was a message from Samira, sent through the official channel. She had found two versions of the route map in the records package. One included Lantern Passage. The other, used in the demonstration, did not.
The second version had been generated forty-eight hours before the test.
At the bottom of her note was one more fact: the change carried a manual override identifier, not the ordinary automated-update label.
May you like
Someone had changed the map. Whether by error, by instruction, or for some other reason, we still had to learn.
I squeezed Lily's hand a little tighter and went upstairs to make dinner. Until we knew more, what mattered most was keeping people safe with the routes we could actually verify.
