He found the file.
The minutes recorded a discussion of the proposed vehicle-control policy. The board had requested revisions and legal review. No motion to adopt the policy had been approved.
Richard read the relevant passage three times.
Then he opened the edited document he had created earlier.
He compared the language.
The draft policy had been altered to suggest that an emergency resolution existed.
Richard had not forged a signature or altered the official minutes, but he had created a document that could mislead a reader about the policy's status.
He knew what he had done.
He also knew that if he submitted the document to the board as proof of authority, the original draft and the meeting minutes would contradict it.
For several minutes, he considered deleting the document.
Then he remembered that the association's system recorded document activity.
Deleting it might not remove the underlying version history, and it could make the situation considerably worse.
He closed the file without changing it.
At 9:12, he received an email from the association's attorney.
The message requested that he provide all documents concerning the Tahoe incident, including the initial notice, subsequent revisions, the towing request, communications with Northstar, and any policy or resolution he believed authorized his actions.
The attorney also instructed Richard not to alter or delete any relevant records.
Richard read the message.
Then he printed it.
For the first time, he began to understand that the incident was no longer simply a disagreement with a resident.
It had become an official governance review.
He would have to answer questions.
He would have to produce records.
And he would have to explain why his conduct had gone beyond what the association's documents permitted.
At 10:00, Nathan Cole received a call from the body shop.
The technician had inspected the Tahoe and confirmed that the rear bumper had sustained damage to its painted surface. The mounting points appeared intact, but the repair would require preparation, repainting, and replacement of a damaged trim section.
The estimate was $1,180.
Nathan wrote down the amount and asked for a formal copy.
Then he called his insurance company.
The representative advised him to retain the video, photographs, witness statement, and repair estimate. Because the damage appeared deliberate, the insurer recommended documenting the incident with local law enforcement and allowing the appropriate process to determine responsibility.
Nathan followed the advice.
He contacted the sheriff's office again, provided the incident reference number, and asked how to submit the video and witness statement.
The deputy assigned to the follow-up arranged to meet him that afternoon.
Nathan did not exaggerate what had happened. He explained that Richard had kicked the vehicle several times, attempted to arrange its removal, and continued to claim enforcement authority after being challenged.
He provided the original footage.
He identified Rachel Dunn as a witness.
He supplied the emails and the repair estimate.
The deputy reviewed the material and explained that the office would document the complaint and assess what further steps were appropriate under local law.
There was no dramatic arrest.
No officer promised an immediate prosecution.
The deputy did not declare Richard guilty simply because the video existed.
Instead, he asked questions, recorded the relevant details, and explained the process.
Nathan appreciated that.
He wanted the incident taken seriously, but he did not want another person to misuse authority by jumping to a conclusion.
When the deputy left, Nathan felt a little more confident that the matter would be handled properly.
At 12:15, Daniel called from the courthouse.
"How did the meeting go?"
"Well enough. The deputy took the footage and the documents."
"Good."
"The repair estimate came in at eleven hundred and eighty dollars."
Daniel nodded.
"Keep the invoice when the work is completed."
"I will."
Nathan hesitated.
"Daniel, I heard something else this morning. Richard has been telling people that he thinks your vehicle is connected to a government investigation."
Daniel closed the file on his desk.
"Did he identify the investigation?"
"No. He apparently told one of the board members that the vehicle might be part of some kind of surveillance operation."
Daniel exhaled slowly.
"That sounds like speculation."
"That's what I thought."
"Don't respond to it. The vehicle belongs to me, and I was visiting you. That's the relevant fact."
Nathan paused.
"Wouldn't it be easier if you told the board who you are?"
"Not necessarily."
"Why?"
"Because my position doesn't make the driveway incident more or less legitimate. The facts are the same whether I work in a courthouse, a warehouse, or a grocery store."
Nathan was quiet.
Daniel continued.
"If the board needs a statement from me, I'll provide one. If law enforcement needs to speak with me, I'll cooperate. But I'm not going to turn a personal dispute into a contest over professional titles."
Nathan understood.
"All right."
They ended the call.
Daniel returned to the procurement review.
The Northstar file had become more complicated, but it remained separate from the HOA complaint.
Laura Bennett had obtained additional records showing that Northstar had billed a county department for several vehicle inspections. The department's own logs did not contain matching entries for two of those inspections.
That discrepancy required an explanation.
It did not yet establish fraud.
The missing records might have been stored elsewhere. The inspections might have been performed by a subcontractor. The invoices might have contained errors that could be corrected.
Daniel and Laura prepared a list of questions for the department's purchasing officer.
They requested original work orders, supporting reports, subcontractor records, and payment authorizations.
They also asked Northstar to identify the employees who had performed the work.