THE MAFIA BOSS HAD SPENT FOUR YEARS HELPING HIS LITTLE DAUGHTER LIVE WITHOUT HER MOTHER, UNTIL A BLEEDING HOUSEMAID REVEALED THAT HIS FUTURE BRIDE WAS SECRETLY PREPARING TO SEND THE CHILD AWAY.

We spent the next forty-eight hours learning how much damage the word routine could hide.

The archive containing passenger confirmations was scheduled for automatic deletion because it had reached the end of its retention period. HarborLine said the process was standard. Tara agreed that retention schedules could be legitimate, but insisted that once a dispute was known, responsive evidence had to be preserved under the applicable requirements.

Our counsel sent a formal preservation demand. HarborLine's lawyers acknowledged receipt and asked for time to determine which systems were affected. Time was exactly what we did not have.

On Thursday morning, Meredith authorized outside counsel to seek urgent court relief if the vendor failed to confirm a reliable preservation hold. She notified the board and recorded the decision. No dramatic raid followed. Nobody kicked down a server-room door. We waited through calls, sworn explanations, and the slow machinery of people trying to agree on the meaning of an electronic file.

Early that morning, I had watched Celeste speak with a woman who needed transportation to an appointment the following day. Celeste explained that the disputed data imports were paused but that a manual voucher could still be issued. The woman asked whether she would have to repeat her whole medical history to a new driver.

“No,” Celeste answered. “The driver needs the pickup, destination, and accessibility information you choose to share for the ride. Your private records stay with the professionals responsible for them.”

The woman asked the question twice, perhaps because she had heard too many promises that sounded similar. Celeste answered the same way both times, without impatience. I watched the woman's shoulders relax. Whatever the court decided about the archive, that conversation was one of the reasons we needed to preserve the program itself rather than close the gate again.

At lunch, June pushed a plate of sandwiches toward me.

“Eat.”

“I'm not hungry.”

“That is not the same as not needing lunch.”

I took half a sandwich.

She sat opposite me. “I used to think people who made good rules would automatically follow them. Now I think a rule is only as good as the person who can question what happens when it's ignored.”

“Are you quoting Sofia?”

“No. She was better at saying things in fewer words.”

We smiled. Then June stared out the window toward the blue gate.

“Amelia asked me yesterday whether her mother's name was being used to trick people,” she said.

“What did you tell her?”

“That somebody was using records associated with the old program in ways we're investigating. That doesn't change what her mother wanted for this place.”

“Did she seem relieved?”

“She said she knew that already. She just wanted an adult to say it.”

I thought about how often children sensed what was happening long before adults found comfortable words for it.

By three, Tara located a second archive at an independent backup service. Access required credentials from a different administrator and written authorization from the custodian. The records appeared to include the original responses from passengers and dispatchers, preserved before the disputed overrides were applied.

“Can we use it?” I asked.

“After we document the source and establish integrity,” she said. “A backup isn't magic. We have to show what it contains and how we obtained it.”

We watched the authorized technician connect through a secured review station. Tara recorded the file identifiers and cryptographic checksums with an independent witness present. The first sample showed an ordinary ride, correctly confirmed by a family. The second showed one of the disputed trips marked completed in the new database but canceled in the archived original.

My pulse quickened.

“That's a contradiction,” I said.

“Yes,” Tara answered. “And now we have a way to examine more of them.”

The backup didn't establish who changed each entry. It did establish that a completed status couldn't safely be trusted without checking the earlier confirmation.

The backup technician also showed us a record that was correct. A grandmother had taken a late-evening ride to a hospital where her grandson was being treated. The driver had recorded an arrival, and the passenger had confirmed it by phone the next morning. The archived and reported entries matched.

“Why spend time on that one?” June asked.

“Because we need to know the system can preserve a true event as well as alter a false one,” Tara replied. “And because a review that searches only for mistakes can mislead us about the size and shape of the problem.”

I wrote that in my notes. It didn't make the bad records less serious. It made the investigation more trustworthy.

Afterward Tara showed me the difference between a screenshot and a preserved source record. A screenshot could be useful, but it didn't show what happened before or after the visible lines. An authenticated export could include a documented sequence of changes, though even that needed interpretation. She asked me to explain the difference back to her as though I were training a new staff member.

I stumbled through the first attempt. She corrected me without impatience. On the second attempt I found the words: “A picture can show what the screen said. A source record can help show how it came to say it.”

“That's good enough to teach,” she said.

At the same time, a judge issued interim preservation directions after the parties submitted their positions. HarborLine agreed to suspend automated destruction of the responsive records while the scope of the dispute was reviewed. There would be further hearings and questions about access, but the files would not vanish that night.

I thought I'd feel triumphant.

Instead, I felt tired enough to cry.

Celeste told me to go home. I insisted I could stay for the family meeting. She shook her head.

“You have spent two days trying to protect other people's time,” she said. “You don't get to spend your own as though it has no value.”

I went home, ate soup with my mother, and slept for nine uninterrupted hours.

The following morning, Blue Harbor held an information session in the community hall. Families could attend in person or call privately. We had arranged interpreters and a child-friendly room with two trained volunteers. We did not display a list of affected families or invite anyone to recount personal medical details before strangers.

Meredith explained the dispute, the preservation steps, and the difference between an inaccurate record and proof of an intentional scheme. June explained how verified transportation would continue. Celeste described the correction process. I answered questions about individual contact points without turning the meeting into a maze of departments.

A man near the front raised his hand.

“Why should we trust you this time?”

Meredith looked directly at him. “You shouldn't have to rely on trust alone. You should have access to your own record, an independent appeal route, and a way to verify whether the correction was made. We'll publish the process and let the advisory group test it.”

A woman behind him asked whether using vouchers would put her private address into another contractor's system. June admitted that necessary trip details would still have to be shared with a chosen provider, but said the program was reviewing what information was essential and how long it could be kept.

“Don't tell me the system is safe because it has a password,” the woman said.

“Fair,” June answered. “We'll tell you which safeguards are in place and what remains under review.”

Near the door, Tessa handed out copies of the official contact sheet. She had asked Leah's permission to volunteer, and Celeste gave her a clear, limited job that did not involve seeing confidential information. Jonah sat beside her with a cardboard rocket perched on his knee.

“Is my rocket allowed at official meetings?” he asked me.

“Only if it doesn't interrupt the speaker.”

“It is a very respectful rocket.”

Leah laughed. For the first time in days, I did too.

After the meeting, Enzo and I walked toward the shore. His phone rang twice. He silenced it without looking.

“Your lawyers?” I asked.

“Probably.”

“You can answer.”

“They can leave a message. I wanted five minutes with you.”

I didn't tell him that the gesture meant more than flowers ever had.

He stopped where the path curved toward the reeds.

“The buyer withdrew from the sale,” he said.

“I'm sorry.”

“I'm disappointed. But it doesn't change the decision.”

“Have you told Amelia?”

“Not the financial details. She knows I'm changing some of my work. She asked whether we can still go to the planetarium.”

“What did you say?”

“That Jupiter remains affordable.”

I leaned against him, and for a moment we stood quietly, watching the gray lake rise and fall.

Then Tara called.

The restored archive showed that many of the disputed trips had no passenger confirmation, while some had explicit cancellation responses that were later overwritten in the reporting layer. A preliminary review linked a subset of those changes to an exception batch exported into a separate billing platform.

“What platform?” I asked.

“A company called Cedar Ridge Analytics,” Tara said. “It received invoices from HarborLine under an administrative services agreement.”

“Who owns it?”

“We haven't established the beneficial ownership. The registered agent isn't enough to draw a conclusion.”

Enzo was listening beside me.

He said quietly, “I remember that name.”

“From where?” I asked.

“An old procurement review. Peter asked me to approve a subcontractor arrangement. I sent it back because Sofia objected to additional data sharing.”

“Did it go forward?”

“I don't know.”