Iris had never forgotten the day the system passed its final acceptance test. The engineers celebrated with stale cake in a meeting room where nobody could open the windows. Senior management praised the project's speed. The testing team had recorded fourteen unresolved exceptions, all categorized as low priority because they did not affect the main dashboard. Iris objected that the dashboard was not the product. The product was the trail left behind every decision to move another person's money.
She kept a copy of that meeting's minutes, along with a version-control report showing when the audit-log setting had been changed. Years later, she and Evelyn spread the documents across the kitchen table and compared them with Nathan's index. They discovered a pattern: during ordinary business hours the system recorded approvals under named users, but certain late-night adjustments passed through a shared service credential. A shared credential could be legitimate for maintenance. It should not have possessed authority to amend trust signatories. The bank had been warned. Somebody had approved the configuration anyway.
Iris explained how an independent reviewer could reconstruct the changes without accessing unrelated clients' confidential information. A forensic copy would be sealed, its integrity verified, and the search scope approved by a neutral decision-maker. Evelyn listened carefully. She wanted the proof recovered, but she did not want a campaign for transparency to become an excuse for violating the privacy of everyone else. They drafted a narrow request and sent it to Priya through the secure channel.
Later, Iris showed Evelyn an old picture of Nathan eating lunch on the steps of a closed rural clinic. He was laughing at something outside the frame. For years Evelyn had remembered him mainly in his last months, when illness reduced his world to appointments and difficult conversations. Seeing him in sunlight, wearing a ridiculous checked shirt, restored another version of him. It did not soften the unanswered financial questions. It reminded her why they mattered.
"It depended on usage. We calculated eight million by the time Nathan retired. That was before the national contract."
Evelyn looked at the coffee cooling beside her. "Why didn't you come forward when we sued?"
"I did. My counsel submitted a declaration. It never appeared on the hearing docket. Later I was told the case had settled. I thought Nathan had chosen not to fight."
"He thought you'd withdrawn."
For a long time neither woman spoke. The damage was not simply the loss of money. It was the years in which two friends had believed the other had abandoned a promise.
The river valley had a habit of testing every system people built beside it. During the spring floods, roads disappeared beneath muddy water, telephone lines failed, and families learned to rely on neighbors who knew which farm tracks remained passable. Iris had moved there after leaving the bank because she wanted a place where technical knowledge carried visible consequences. A warning ignored could mean a wet basement. A pump repaired in time could save a crop. She liked the honesty of those relationships.
When Evelyn visited again, Iris took her to a county emergency office where volunteers were reviewing flood maps. A coordinator explained how the office recorded reports from residents. Some reports were inaccurate. Others appeared trivial until several were combined. A single flooded ditch might be ordinary; five reports in the same hour could indicate a blocked drainage system. The office kept the original reports even when they were later corrected, because an honest history of decisions mattered during the next storm.
Evelyn saw the comparison immediately. "Your flood map doesn't erase the first warning when the water level changes," she said.
"Exactly," Iris replied. "You keep what people knew at the time. Otherwise you can't learn from the choices they made."
They returned to Iris's house with a better understanding of the bank's software problem. The old interface had allowed an authorized user to overwrite certain fields without presenting a meaningful history to ordinary reviewers. The new proposed design would show a chain of changes, each with a reason and verified authority. Iris made Evelyn test a simple prototype using imaginary grant entries. When Evelyn selected an invalid beneficiary, the interface requested additional approval and displayed the consequences for scheduled payments. It did not treat her as foolish. It told her what the action would do.