Chapter 44 - ONE HUNDRED AND TWELVE
The number was one hundred and twelve.
It appeared in a controlled technical report released to the authorized response team on a bright Monday morning. One hundred and twelve historical route records had been imported through a field mapping that could overwrite current location information. It did not mean one hundred and twelve families had been sent to the wrong place. It did not mean that every record had been viewed by an unauthorized person. It meant there were one hundred and twelve entries requiring individual verification and appropriate notice.
I wrote those qualifications at the top of my notebook before anyone could turn the number into a slogan.
Celeste called a meeting with the family-response team, Priya, and the privacy officer. We divided the work into confirmed inaccurate destinations, records with a potential conflict requiring verification, and records shown by logs to have been rejected before use. Families in each category would receive information appropriate to their actual situation. We would not frighten people with the broadest possible allegation simply because it made a forceful public statement.
“I know some families will want a single number,” Celeste said. “We can give them one, with the explanation. But each family deserves to know their own status as accurately as we can determine it.”
By afternoon the report had leaked to a local blog. The headline read: 112 FAMILIES SENT TO WRONG ADDRESSES BY BLUE HARBOR. It was false. The text underneath quoted a sentence from the technical report without its surrounding limits. Our communications officer requested a correction and issued a public summary of the verified categories. We did not demand the story disappear. We asked that it be made accurate.
Leah called that evening. “I saw the headline,” she said. “Jonah saw the number. He asked if there were one hundred and eleven kids like him.”
“I'm sorry. The number describes records, not children or confirmed incidents. Would you like me to explain what it means in language he can understand?”
“Yes. But let me decide when. He's finishing a school assignment.”
“Of course.”
She called back after dinner, and Jonah asked his question directly. I told him that an old computer file had been used in a way it shouldn't have been, and that adults were checking each record to see whether anybody's travel details had actually been wrong. He listened, then said, “So there are one hundred and twelve things to check, not one hundred and twelve people in trouble.”
“Exactly.”
“That's still a lot.”
“It is.”
“Then maybe they need more than one checker.”
I smiled. “They have a whole team.”
He sounded reassured enough to return to his assignment. Leah thanked me for not making him feel foolish. I told her his question was better than several questions I'd heard from adults.
The next day Pilar insisted on including a family advocate in the design of the notice letters. She didn't ask to see other people's private records. She asked to review the wording, the available contact methods, and the steps someone would need to take to challenge a result. Her first change was to remove the phrase DATA REMEDIATION EVENT.
“Just say a record may be wrong,” she told us. “People know what wrong means.”
She crossed out another sentence that promised “seamless resolution.” “Don't promise seamless anything,” she said. “If somebody has to spend a morning on the phone, it has a seam.”
I wanted to frame the draft after she finished. It was marked up in green ink, with arrows pointing toward every phrase that seemed designed to protect the organization from embarrassment rather than help the person reading it.
At the office we began processing individual corrections. Some families had moved legitimately, and the historical feed had not affected their current route. Some found a wrong code that had never reached a driver. Eleven cases required further examination because a booking or confirmation appeared to have used the wrong location. The count might change as the audit progressed. We made that uncertainty clear.
Walter and his wife were among the eleven. His wife's missed therapy trip now had a documented technical cause: the system had substituted the old outreach office code for her current pickup location. The provider corrected the no-show record, reimbursed eligible costs through the established process, and supplied a manual confirmation arrangement for future trips. Walter accepted the written correction without calling it justice.
“I'm glad they finally wrote what happened,” he told me. “But she still missed treatment. Somebody should remember that when they count the cases.”
“We will.”
I added his words, with permission, to the internal impact summary. Not as a dramatic quote, but as a reminder that an error log could be accurate and still too small to describe its consequences.
At the weekly advisory meeting June asked whether the public should see the whole technical report. Priya explained that a redacted version could be released after privacy and legal review, but the raw data could not simply be posted online. One member worried that withholding information would resemble the old secrecy. Another pointed out that publishing every address would create exactly the harm the review was meant to stop.
Pilar ended the argument. “We can demand the truth without demanding other people's secrets,” she said.
The room settled around that sentence. It didn't solve the redaction questions, but it gave the discussion a shared purpose.
Before I went home, the privacy officer showed our team how the individual correction portal would work for people who did not use smartphones. There would be a staffed phone route, a paper request option, and assistance available in languages used by participants. One colleague asked whether those alternatives were inefficient. Pilar answered from the end of the table: “An efficient system nobody can access isn't efficient for the people it excludes.” Celeste wrote the remark on the whiteboard and asked that the next test include participants who used each contact method.
At home I found Enzo and Amelia building a model of a suspension bridge. Their table was covered with thread, popsicle sticks, and a ruler. Amelia had assigned her father the job of holding the structure while she adjusted the tension. He obeyed with the solemn concentration of a man guarding state secrets.
“Don't move,” she told him.
“I haven't.”
“You blinked.”
“Is that prohibited?”
“During the final test, maybe.”
I put down my bag and laughed. Amelia looked up. “We have a hundred and twelve reasons to test this bridge,” she announced.
I blinked. “Where did you hear that number?”
“On the news. Dad explained it's about records, not accidents. I thought it made a good engineering number.”
Enzo looked worried. “I didn't know whether to tell her anything.”
“She already heard it,” I said. “You helped her understand.”
Amelia pointed at the bridge. “Now we're testing one hundred and twelve little weights. Except we only have forty buttons, so we're doing three rounds.”
“That's resourceful,” I said.
“It's not statistically perfect,” she replied. “But it might reveal a weakness.”
After dinner I helped them count buttons into jars. Amelia's bridge collapsed at the eighty-seventh weight. She was furious for three minutes, then began redesigning the supports. Watching her, I thought about how differently adults often responded to system failure. We wanted to hide the collapse, explain it away, or blame the person who placed the weight. Amelia wanted to see which joint broke.
The following afternoon Celeste received a status report from the independent assessor. The mapping rule had been disabled across all identified participating systems, and the team was testing for unlisted downstream copies. The report did not certify that every possible copy was gone. That would take longer and might require negotiations with former vendors. The eleven bookings under close review were being checked against driver records and family accounts.
A second finding was more troubling. One of the old exports had been generated after the project termination date, using a service credential that should no longer have existed. Its renewal had been recorded in a maintenance ticket approved under Mallory Keene's delegated authority. Her office said the renewal was intended only to preserve emergency continuity. Investigators would have to determine whether the ticket permitted the use that actually occurred.
When I told June the verified summary, she closed her eyes briefly. “Somebody kept the door open because they were afraid of losing access,” she said. “Then other people walked through without asking.”
“That's what it looks like. We still have to establish who did what.”
She nodded. “I don't want punishment based on guesses. I want a door that closes when the people it protects say close it.”
May you like
Before I left, she asked me to help hang a new sign beside the program contact board. It explained how participants could request a copy of their own corrected travel information, how to appeal, and how to withdraw from optional data sharing. The print was large. The language was plain. There was a phone number for assistance.
I stepped back to look at it. The sign wasn't glamorous. It would never make a headline. But it converted the frightening number into a set of choices real people could use. Outside, the blue gate swung gently in the spring wind. It had a lock, a hinge, and a person responsible for checking both. I wished the digital world had learned that lesson sooner.
