She made mistakes during the demonstration, including approving a date that fell on a public holiday. Iris showed her how the system flagged the issue and allowed a documented correction. Evelyn appreciated that the design assumed honest people would sometimes err. Accountability did not require pretending mistakes could be eliminated. It required making them visible and repairable.
Before leaving, Evelyn helped Iris tighten a loose railing on the porch. The work was awkward with two people holding tools at different angles. They laughed when the bolt fell into a flowerpot and spent ten minutes searching for it. The railing was secure by the time Evelyn departed. On the drive back, she thought of the bank's grand declarations about trust. They were less persuasive now than a good bolt, properly fitted, that somebody would check again after the next storm.
The drive to Iris Bell's house took Evelyn across a bridge where the river rose so close to the road that the guardrails seemed to float. She remembered making the journey with Nathan when they were younger and still argued about directions. He had insisted on carrying a folded paper map even after their daughter bought them a navigation device. "It works when the signal doesn't," he said. Evelyn had teased him about being born in the wrong century. Later, during a storm, the map had helped them find a clinic where the power was out.
Iris met her at the door with a wrench in one hand. A weather sensor had come loose, and she was trying to repair it before the rain. Her greeting was brisk, but her eyes softened when she saw Evelyn. Inside, the kitchen contained the organized disorder of a person who treated every problem as solvable with patience, tools, and an adequate supply of labels.
They spoke first about Nathan. Iris remembered his insistence that software designers spend a morning at the receiving end of their decisions. He had once brought her to a clinic where a grant payment arrived late. A nurse showed her the locked medication cabinet and explained what a missing authorization meant in practice. Since then Iris had refused to design financial workflows without exceptions that could be investigated by humans.
"That made him unpopular," Iris said. "Some people think an exception is a nuisance. Nathan knew it could be a warning."
Evelyn placed the check on the table between them. Iris used a magnifying glass to inspect the notation, then pulled out a notebook that contained dates in columns. She did not react dramatically to the amount.
"The money may not be where the ledger says it is," Iris told her. "But the history of the commands might still exist. If someone altered the trust's status, they had to make a sequence of choices. Those choices leave fingerprints."
Iris returned to the bank's technical review with a question that none of the engineers had initially considered: what happened when an employee tried to correct an error? The old system allowed changes but did not consistently explain how corrections affected linked approvals. A user could fix one field and unknowingly leave another record inconsistent. The investigation had found several discrepancies caused by attempts to repair earlier mistakes, making it harder to distinguish negligence from deliberate manipulation.
The engineers developed a correction process that displayed the original entry, the proposed change, the reason for it, and the downstream records affected. A separate reviewer could approve the correction, and the history remained visible. Iris tested it with an example involving a clinic whose street name had changed after a municipal boundary adjustment. The system initially treated the new address as an unrelated beneficiary. The team refined the workflow so legitimate corrections could proceed without weakening identity verification.
A junior developer asked whether they should design against every conceivable misuse. Iris said no system could anticipate everything. They should document assumptions, test consequential failures, and create a way for users to report problems without being punished for noticing them. The developer looked relieved. He had spent weeks afraid that one missed scenario would make him responsible for the next scandal.
At the final workshop, Gabriel described how the new process would be taught to staff. Iris asked him to include examples of both honest mistakes and suspicious patterns. Fear alone would encourage employees to hide errors. Good training would show them what to do when an error occurred and how to escalate a concern they could not explain.
The prototype was not perfect. Its first version required too many clicks, and a community trustee struggled to understand one warning. They changed it. Iris found the revision satisfying precisely because someone had been willing to say the design did not yet work.