For Richard, that was more difficult than facing the possibility of financial consequences.
He opened his computer and drafted a message to the neighborhood.
He wrote that the association was reviewing a technical question concerning guest parking. He claimed that his actions had been taken in good faith to protect the community.
He did not mention the kicks.
He did not mention the unapproved document.
He did not mention the failed tow.
He described the incident as a misunderstanding.
Then he added a final paragraph.
Residents should be cautious about accepting outside claims that undermine the association's authority. We will continue to enforce all valid community rules.
He sent the message.
Within minutes, replies began arriving.
One resident asked whether the association had approved the emergency policy.
Another asked why Richard had attempted to tow a vehicle from a private driveway.
A third asked whether the board had received the security footage.
Margaret Lewis asked for the payment records relating to Northstar.
Richard closed his email.
He had intended to end the discussion.
Instead, he had given the neighborhood another reason to ask questions.
At 11:20, the county prosecutor's office received a package of documents from Northstar Compliance Services.
The package contained copies of invoices, work orders, subcontractor agreements, and internal approval records.
Laura Bennett began reviewing them.
Daniel worked through the morning on an unrelated financial case.
At lunchtime, Laura appeared at his door.
"I think we need to look at one of the subcontractor records more closely."
Daniel set down his pen.
"What did you find?"
Laura placed a page on his desk.
It listed a subcontractor who had performed vehicle documentation services for Northstar.
The company's name was Willow Ridge Field Operations.
Its registered address was a commercial unit in a neighboring county.
The company had no employees listed in the public filing.
Its invoices showed payments for inspections and administrative support.
Laura pointed to a line near the bottom of the page.
"One of the work orders was entered under an emergency vehicle-control category."
Daniel read the description.
It was similar to the wording in Richard's notice.
He looked at Laura.
"Do we know who requested the work?"
"The records list an account contact associated with Willow Creek Estates."
"Name?"
"Richard Harlan."
Daniel leaned back.
The connection was becoming more concrete, but it still required careful examination.
A private association president could hire a contractor whose company later appeared in a public procurement file without committing any offense. The work might be legitimate. The shared language might reflect a standard template. The invoice might have been properly authorized.
What mattered was whether the records accurately described the work performed and whether the payments were supported by valid contracts.
"Let's obtain the complete file," Daniel said. "We need the contract, the authorization, the deliverables, and proof of payment. We also need to know whether the subcontractor actually performed the work."
Laura nodded.
"And the HOA dispute?"
"Separate unless the evidence establishes a relevant connection. We cannot use my family situation as a shortcut around the ordinary review process."
"Understood."
Daniel looked at the document again.
The account entry was dated six months earlier.
That meant the contractor relationship had existed long before the Tahoe incident.
It did not establish that Richard had planned the driveway dispute.
It did not establish that the HOA had misused money.
It simply meant that the company deserved a closer look within the scope of the procurement inquiry.
Laura returned to her office.
Daniel remained at his desk.
For the first time, he began to wonder whether Richard's obsession with enforcement reflected something beyond personal arrogance.
Perhaps it did not.
Perhaps the man simply enjoyed authority.
But if the records revealed that Northstar had been paid for services that were never performed, or that invoices had been submitted under categories designed to avoid scrutiny, the consequences could extend beyond the HOA.
Daniel made a note to discuss the potential overlap with the office's supervising prosecutor.
Then he returned to work.
At 2:15, Nathan called.
"The board has scheduled the special meeting for tomorrow evening."
"Good."
"They've asked me to attend."
"Will you?"
"Yes."
"Keep your statement factual. Answer what they ask. Don't speculate about the contractor invoices."
"I won't."
Nathan paused.
"There's something else. Richard has started telling people that the SUV may be connected to an investigation."
Daniel's expression changed.
"What investigation?"
"He hasn't said. One neighbor told Emily that Richard claimed the vehicle was suspicious because it belonged to someone connected to law enforcement."
Daniel was silent for a moment.
"Did Richard identify me?"
"Not by name. But he described the visitor as someone who had been questioning his authority."
Daniel considered the implications.
Richard might have guessed that Daniel worked in government. He might have inferred it from the way Daniel spoke, or from the fact that he had asked for written authorization rather than simply arguing.
Or Richard might have been attempting to make the incident sound more serious than it was.
Either way, Daniel did not intend to respond to neighborhood rumors.
"Let him make whatever statements he chooses," Daniel said. "You don't need to correct them unless they affect the board's review. Keep the focus on the damage and the unauthorized tow attempt."
Nathan agreed.
They ended the call.
That afternoon, Richard received an email from the association's attorney requesting a meeting before the special board session.
The attorney wanted copies of the documents Richard had cited, an explanation of the towing request, and confirmation of who had authorized the security inspection.
Richard replied that he would provide the information at the meeting.