ORCHID MARK

Chapter Seventy-Six — The Account Code

        "Money does not disappear. It moves. The movement always leaves a record, if the person looking

             knows which account codes to follow and has enough patience to follow them all the way to the

                                                                                          end."

Aldridge called on Monday morning at seven forty-five.

"The account code," she said, without preamble.

"Yes?" Fae said.

"It is not a legal violation. The emergency stabilization was coded correctly under the regional emergency protocol that protocol allows the emergency account to be used for infrastructure stabilization regardless of outstanding community fund allocations."

"So on paper …"

"On paper the redirect and the emergency stabilization are both legitimate," Aldridge said. "The community fund was redirected through a process that was technically within the governance rules of the time. The emergency stabilization was authorized under a separate protocol that was legitimately applicable."

Fae was at the kitchen counter with coffee and Ruth Callahan's folders open in front of her.

"But," she said.

"But," Aldridge said, "the combination of the two  redirects plus emergency coding meant that Brackmore's outstanding community fund allocation never appeared as outstanding in any subsequent allocation model. Which means every disbursement decision since has treated Brackmore as a community with no infrastructure deficit."

"Which is incorrect."

"Which is technically compliant and substantively incorrect," Aldridge said. "That distinction is the argument."

Fae looked at the folders.

"Can we make it?" she said.

"We can make it in the governance challenge," Aldridge said. "The clause gives the governance chair standing to challenge disbursement decisions that do not reflect the substantive condition of the communities concerned. The account code discrepancy is the evidence that the current allocation model does not reflect substantive conditions." A pause. "It is a strong argument. It will not be quick."

"How long?"

"The initial challenge at the session triggers a review period," Aldridge said. "Standard review is sixty days. I am going to argue for thirty on the basis of the provision proceedings timeline the families in the proceedings are waiting on disbursement decisions, and a sixty-day review extends their wait unnecessarily."

"Crane will argue for ninety."

"Yes," Aldridge said. "He will cite process integrity. He will be correct that process integrity requires adequate review time and incorrect that ninety days is the minimum adequate time."

"And the arbiter panel?"

"If Crane challenges the governance decision to trigger the review, the clause resolution mechanism applies." A pause. "The arbiter panel includes the infrastructure specialist with prior knowledge of the Brackmore surveys."

Fae was quiet.

"He knows that," she said.

"He knows that," Aldridge agreed. "Which is why I think his more likely move is not to challenge the governance trigger directly but to challenge the evidence specifically the account code interpretation. He will argue that technical compliance is sufficient and substantive assessment exceeds the governance chair's remit."

"Does it?"

"No," Aldridge said. "The joint clause definition specifically includes substantive community outcome assessment in the governance chair's remit. We wrote it that way deliberately."

Fae looked at her notebook.

"We did," she said.

After she hung up she sat for a moment with Ruth Callahan's folders and her notebook and the account code diagram she had drawn out the previous evening the redirect, the emergency stabilization, the subsequent allocation models, each step technically compliant and collectively producing nine years of an incorrectly calibrated disbursement model for forty-three families.

She thought about the quay at sixty percent capacity.

She thought about the report from eleven years ago that said the infrastructure investment was being appropriately allocated.

She thought: the clause was written for exactly this.

She called Derek.

"The challenge is solid," she said.

"When?" he said.

"The next session," she said. "Three weeks."

"Crane."

"Crane will argue the account code interpretation," she said. "Aldridge and I will counter. The arbiter panel is the backstop if he forces the mechanism." She paused. "I need you to do one thing."

"What?"

"In the session, when I trigger the governance challenge, do not respond immediately. Let the mechanism run. Do not offer a counter-position from the executive chair before the governance process has completed."

A pause.

"You're asking me not to manage it," he said.

"I'm asking you to trust the structure," she said. "Again."

A longer pause.

"All right," he said.

She looked at the folders.

"Thank you," she said.

"Don't thank me," he said. "Just win."

She looked at the account code diagram.

"Yes," she said.

She spent the afternoon building the challenge document.

It was twenty-two pages when she finished, which was fourteen more pages than she had expected and exactly as many as the argument required.

She sent it to Aldridge at six-thirty.

Aldridge replied at eight: This is thorough.

Fae replied: It needs to be.

Aldridge: It is. He's going to know you've been to Brackmore.

Fae: Good. He should know that what he redirected, someone has now gone and looked at.

A pause.

Then Aldridge: I'll have my annotations back to you by Wednesday.

Fae looked at the message.

She looked at the twenty-two pages.

She thought about Ruth Callahan's filing cabinet and the three folders and nine years of documents that were exactly what they appeared to be.

She closed the laptop.

She went to bed.

She slept without difficulty, which was how she knew the preparation was right.