By early spring, the orchard floor was soft with new growth, and the frost warnings had begun arriving from the county weather service. Samuel kept his old notebook beside the kitchen radio, marking temperature forecasts and bloom stages in the margins. He had more confidence in the trees than he did in the weather, but experience had taught him that confidence did not prevent a cold night from doing damage. He walked the rows at dusk and watched the pale blossoms move against a darkening sky, thinking of Eleanor and the season she never got to see.
Tessa called one morning while he was checking a damaged irrigation valve. She had been invited to speak at a Bridgeville regional training session about the revised supplier-dispute process and wanted permission to use a redacted version of the Heritage case as an example. Samuel told her the cooperative owned its records collectively and that he would ask the board for approval. She thanked him for not treating his position as the same thing as the board's authority.
"You've been teaching us that distinction," he said.
"I think your wife was teaching you long before I did."
Samuel laughed softly. "She was. I just didn't always listen the first time."
The board approved the example after removing personal financial details that did not need to be shared. Tessa built the session around three versions of the same event: the original receiving entry, the final summary that had led to a deduction, and the complete event history showing the change between them. She did not put Graham's photograph on the screen or describe the case as a morality play. She asked participants to identify what could be verified from each record and what remained unknown without a second inspection.
A produce supervisor from another store raised his hand. "If the original receiving decision is wrong, why shouldn't a manager fix it immediately?"
"They should," Tessa answered. "But the correction needs to preserve the original decision, explain why it was wrong, and identify the evidence supporting the new one. A changed answer doesn't mean the earlier answer never happened."
Another manager asked whether the new controls would make it harder to meet shrink targets. Nadine, sitting near the back, answered before Tessa could. She said Bridgeville had begun evaluating stores on actual handling improvements, documented losses, and adherence to quality procedures rather than rewarding a low shrink figure without understanding the classifications behind it. A store that recorded a real loss honestly would not automatically be treated as worse than a store that moved the same loss to a supplier's account. The distinction was becoming part of management performance reviews, though she acknowledged it would take time to make the practice consistent.
After the session, a young receiving associate approached Tessa with a question about an intake mistake she had made the previous week. She had entered the wrong quantity, discovered it after the truck departed, and worried that correcting the number would make her appear careless. Tessa asked whether she still had the driver's signed receipt and whether the actual cases could be counted. When the associate said yes, Tessa explained how to submit a visible correction with the supporting documents.
"A mistake you can trace is easier to fix than a perfect-looking record nobody can explain," she told her.
The young woman nodded and wrote down the steps. Watching her, Tessa remembered her first year at Bridgeville, when she had been terrified of making an error in front of a supervisor. She would have benefited from someone telling her that accuracy was not the same thing as never being wrong. Now she had an opportunity to say it to people who might need to hear it before the pressure became a crisis.