Chapter 38 - THE HOUSE WITH NO NUMBER
The vacant house was blue, though not the blue of our gate. Its paint had faded to a tired gray around the windows, and one porch step sagged toward the sidewalk. A bright orange demolition notice hung beside the door. From the curb it looked unremarkable, the sort of neglected building people walked past without noticing.
I was there with the independent technical assessor, a city property official, and a community advocate who had been asked to witness a limited location check. We had permission to inspect the exterior and confirm the address. We were not entering an abandoned structure, and we certainly weren't there to search for secret files beneath the floorboards. The reason for the visit was simpler: four unrelated transport records had pointed to this house. We needed to understand whether the address had once served a legitimate administrative purpose.
The property official, a woman named Maribel Scott, opened a municipal map on her tablet. “This parcel was used as a temporary outreach office nearly seven years ago,” she said. “Not as anyone's home. The office was closed before the building was sold.”
The assessor looked up. “Did the outreach program coordinate emergency transportation?”
“Some referrals, yes. I can find the public program description. Any private records would have to be requested through the proper office.”
I stared at the orange notice. The wrong address was not a random keystroke after all. It was an administrative location repurposed by software as if it belonged to a family. An ordinary old office had become the imaginary home of people who had never lived there.
As we walked back toward the corner, a neighbor called from her porch. She wanted to know why officials kept visiting the house. We explained that we were verifying historical address information without discussing individual clients. She told us delivery vans had once stopped there in the evenings, and that a sign with a different street number had hung over the door before the outreach office closed.
“Do you remember the number?” Maribel asked.
The woman shrugged. “Not exactly. But I have a picture from a block party. My grandson was in front of the house, making a terrible face. If it's useful, I can look.”
We gave her the public contact number. We didn't ask to rummage through her phone. She laughed when I thanked her and said the picture would probably embarrass her grandson more than it helped anybody.
Back at Blue Harbor, the assessor compared the parcel history with the disputed import logs. The software had mapped a historic outreach office identifier to a household field during a later conversion. It was a technical error with an identifiable path. The troubling question was why the outdated file had been included in the conversion at all, despite policies calling for its return or deletion.
Nia read the preliminary mapping explanation and drew a small diagram on a whiteboard. “So the old office was supposed to be a contact point, not a pickup point,” she said. “Then somebody changed what the field meant.”
“That's one possible summary,” the assessor replied. “We're verifying the transformation rules and approval history.”
“And the screen didn't tell me that,” Nia said.
“No. It labeled the result current.”
She put down the marker. “I want that part in the correction. Drivers should know when a route came from an old reference rather than a confirmed family request.”
Her suggestion went into the operational recommendation list. It was the kind of idea an executive might never have thought to ask for, because executives rarely sat in a vehicle trying to decide which address to trust while a parent waited at a clinic.
After work I visited June at the center. She was repairing a broken drawer with a screwdriver she had apparently owned since the first administration of the universe. Amelia and Jonah were at a table making signs for the spring reading fair. They had decided the fair needed a map, though both disagreed about where to place the cookie stand.
“Are you going to make us fill out a route confirmation?” Jonah asked when he heard me mention maps.
“Only if the cookies travel by licensed vehicle,” I said.
He grinned. “Then they can teleport.”
Amelia rolled her eyes. “Teleporting cookies would have terrible safety standards.”
Their argument continued so cheerfully that I let them have it. June pulled me aside and asked how the families were doing. I told her several had accepted manual confirmations and some were still frustrated by delays. She nodded. “A system can be safer and still be inconvenient. We need to admit both.”
A volunteer brought in a donated box of lamps. The center needed more light in the reading room, and June asked whether I wanted to help test them. One flickered. Another lacked a switch. The third worked beautifully but was missing a shade. We argued about whether a lamp without a shade was more useful than a shade without a lamp. It was an absurd debate, and I was grateful for every minute of it.
At home Enzo had left me a message asking if I'd like to accompany him to a public forum on technology procurement. I almost laughed at how much our social calendar had changed. A year earlier he might have invited me to a restaurant with a private room and a reservation made by somebody else. Now he was asking me to sit through a panel discussion about records management.
I called him. “Is this your idea of romance?”
“It's at seven. There may be terrible coffee.”
“You're making it irresistible.”
“I thought you might enjoy asking a difficult question.”
“I can do that for free at home.”
He laughed. We agreed to go separately and meet afterward for dinner, because the forum concerned some of his past business decisions and I did not want my presence to imply that I represented his interests.
The forum took place in a high school auditorium. Speakers discussed procurement rules, public records, privacy safeguards, and the problem of legacy systems after contracts ended. I expected to learn something technical. Instead the most striking comment came from an elderly woman who raised her hand during questions.
“My husband used the same home address for forty years,” she said. “One day your computer decided he lived at a hospital. I spent months proving to strangers where we slept. What does your software call that kind of mistake?”
The moderator looked embarrassed. The technical specialist answered that the industry called it an identity resolution error. The woman waited, then said, “Then perhaps you should call it a person losing control over their own name.”
The room applauded. I didn't know whether applause would change anyone's budget, but the correction entered the public conversation.
During the question period a student asked whether data minimization meant refusing to collect anything useful. The panelist explained that it meant collecting information for a defined purpose, restricting access, and deciding when it was no longer needed. The student asked who checked those decisions after the people who designed the project had left. Several panelists hesitated. Finally an auditor said that independent review and contractual proof mattered precisely because staff changed and memories failed. I wrote the exchange in my notebook. It was a younger version of Sofia's old question, and it deserved a better answer than another promise that technology would handle itself.
Afterward Enzo and I walked to a small restaurant. He told me he had felt exposed when the speakers discussed old feasibility studies. Nobody mentioned his name. Still, he recognized the easy language of innovation and efficiency that had once persuaded him to overlook harder questions.
“I kept thinking about Sofia,” he said. “How I told her she was slowing the project down.”
“What would you say if she were here?”
“That she was right to slow me down.” He paused. “And that I was wrong to confuse urgency with wisdom.”
We sat in a booth beneath a window fogged by the cold. I reached across the table and touched his hand. “You can make that admission without making her a symbol of your redemption.”
He nodded. “She deserves better than that.”
The next morning Maribel forwarded the public parcel photograph the neighbor had volunteered. The old outreach office sign was visible over the doorway. Beneath it was a smaller placard: COMMUNITY ROUTE CONFIRMATION DESK. The image provided a plausible explanation for the obsolete code. It did not identify who had later misused the file.
May you like
More important, the photograph contained a date that didn't match the closure date in the software registry. The office sign had remained for nine months after the registry listed the location inactive. That discrepancy meant at least one official record had been updated late or incorrectly. It widened the task, but it also made the investigation more precise.
I added the photograph to the timeline with its provenance noted and the neighbor's consent documented. Then I looked at the blue gate drawing on my desk, a copy of Tessa's work she'd chosen to share with staff. The gate was crooked in the picture. The rocket was even more crooked. But the people walking through it had faces, names, and a place to go. That was the difference between a route and a record that merely pretended to know where somebody belonged.
