His wife, Susan, stood in the doorway.
"Richard, why are you still dealing with that car?"
"Because people need to understand that the rules mean something."
"Is the rule actually approved?"
Richard did not look up.
"The board has discussed the issue."
"That's not what I asked."
He turned toward her.
"Do you want to start this again?"
Susan folded her arms.
"I'm asking whether the board approved the policy."
"The board has given me enforcement authority."
"Over private driveways?"
Richard's face tightened.
Susan had asked too many questions lately.
She had questioned the new landscaping contract. She had asked why he was receiving so many emails from Gregory Pike at Northstar. She had even suggested that he step down from the board after their last argument.
He considered her questions disloyal.
"I know what I'm doing," he said.
Susan looked at him for a long moment.
"Then why are you so angry?"
Richard returned to the photographs.
"Because people are refusing to respect the association."
She shook her head.
"No. You're angry because somebody isn't afraid of you."
Richard stood.
"That's enough."
Susan left the room.
He sat down again and opened the association's enforcement database.
The system contained records of violations, notices, administrative expenses, and contractor invoices.
Richard had access to the system because of his position.
He clicked on the vehicle-enforcement section.
There were several entries involving Northstar Compliance Services.
Some concerned abandoned vehicles. Others involved alleged parking violations. A few were marked as emergency interventions.
Richard opened the latest entry.
The Tahoe's registration number had been added that afternoon.
The record described the vehicle as an unauthorized commercial vehicle occupying a restricted residential area.
Richard had entered the description himself.
He knew the vehicle was not visibly marked as commercial.
He also knew the property was a private driveway.
But he believed that if he described the matter as a security concern, the association's management company would be more likely to support him.
He clicked SAVE.
Then he opened a separate file containing a proposed enforcement amendment.
The document had been drafted months earlier by Gregory Pike.
It would give the association broad discretion to classify vehicles as temporary security risks and authorize contracted monitoring services to investigate suspected violations.
The proposal had never been approved.
Two board members had objected to its vague language.
The association's attorney had recommended a complete rewrite.
Richard had kept the document anyway.
Now he began editing it.
He changed the title.
He removed several references to the board's pending review.
He added language suggesting that the policy had been adopted as part of an earlier emergency-resolution process.
He did not forge anyone else's signature.
He did something more subtle.
He created a document that could be mistaken for an official policy by someone who did not know the board's records.
It was the kind of shortcut he had used before.
A notice written in authoritative language.
A reference to a rule that had never been formally adopted.
A deadline that sounded legally binding.
Most people did not investigate such things.
They simply complied.
Richard saved the document and printed two copies.
Then he looked at the Tahoe's photograph.
Tomorrow, he decided, the situation would be different.
He would send another notice.
He would request a formal hearing.
He would make sure the homeowner understood that resistance had consequences.
And if that failed, he would find another way to make the vehicle disappear.
He did not know that his access to the enforcement database was already logged.
He did not know that the property manager had begun preserving the original work orders.
He did not know that Linda Price had sent the disputed documents to the association's attorney.
And he did not know that Daniel Mercer had spent years learning how to recognize the difference between a legitimate administrative process and an attempt to manufacture authority.
Most importantly, Richard did not know that the SUV he had kicked belonged to a man whose professional life revolved around the careful examination of decisions exactly like his.
The next morning began quietly.
At 6:45, Daniel woke before the alarm.
He showered, dressed in dark trousers and a plain gray shirt, and reviewed his schedule over coffee.
Nathan was already in the kitchen.
"Morning."
"Morning."
"Any messages from Richard?"
"Nothing yet."
Nathan looked relieved.
"Maybe he finally realized this isn't worth it."
Daniel glanced at his phone.
"Maybe."
He did not believe it.
At 7:12, he received a message from Laura Bennett.
I found a possible link between Northstar and the association records you mentioned. Call me before you leave for the courthouse.
Daniel read the message carefully.
He replied that he would call in ten minutes.
Nathan noticed his expression.
"Work?"
"Yes."
"Something serious?"
"Possibly. I need to verify a few details."
Daniel went upstairs, opened his briefcase, and retrieved the preliminary Northstar file.
He did not take the HOA documents with him. They belonged to Nathan and the association, and he had not yet established any reason to treat them as official evidence in his work.
Instead, he reviewed the procurement records already in his possession.
Northstar had received several contracts through a county purchasing office. The invoices appeared ordinary at first glance, but the payment dates did not always align with the work orders. Some invoices described inspections that could not be confirmed in the agencies' records.
The amounts were relatively small.
That made the discrepancies easier to overlook.
Laura had been comparing the invoices with contractor logs. She suspected that Northstar had billed for services performed by other companies, then claimed administrative fees that were not clearly authorized by the contracts.