“Yes. With a statement explaining that it was presented by your neighbor as authorization for work on your property.”
I sat back.
For the first time, I allowed myself to consider the possibility that Celeste had not simply misunderstood the records.
She had brought a document bearing an official-looking seal, cited a case number that could not be found, claimed an objection deadline had expired, and used that deadline to justify dismantling private property.
If the document had been generated by an unauthorized person, the matter could extend beyond an ordinary property dispute.
But we still needed to know where it came from.
That evening, Sarah and I sat at the kitchen table while Ellen explained the next steps.
The county would conduct its own verification process. The sheriff's office would retain the incident report and photographs. Our attorney would continue seeking the original notice, the service records, and the documents Celeste claimed supported her access rights.
We would not contact Celeste directly about the allegations.
We would not post accusations online.
We would not attempt to remove the survey stakes ourselves.
And we would not allow anyone onto the property simply because they arrived with a clipboard.
“Everything goes through the proper channels,” Ellen said.
Sarah nodded.
“That's fine with me.”
I asked the question that had been bothering me since the deputy left.
“What happens if Celeste knows the notice isn't valid?”
Ellen paused.
“If she knowingly presented a false document as official authority, that could have serious consequences. But knowledge and intent are facts that must be established. We cannot infer them solely from the document's appearance.”
I looked at the photographs of the arbor.
“What about the damage?”
“That is a separate issue. We can pursue compensation and, if appropriate, seek an order preventing further unauthorized entry or interference. We need to evaluate the available evidence and the applicable law.”
After the call ended, I went outside.
The evening air had turned cold. A line of clouds was gathering over the mountains, and the grass carried the damp smell of approaching rain.
The arbor looked worse than it had the day before.
Perhaps that was because I had spent so much time looking at it.
The broken crosspieces had been moved into a neat stack beside the shed. We had not thrown anything away. The damaged grapevine was tied to temporary supports, and Sarah had placed small markers beside the uprooted stones so that we could document their original positions.
I stood beneath the remaining frame.
I could still picture my grandfather working there.
He had been a quiet man who rarely spoke about anything he couldn't demonstrate with his hands. When he built the arbor, he explained every joint, every measurement, and every choice of material.
“Wood moves,” he had told me. “The weather changes. The ground shifts. You build for those things. But you don't build as if the people who come after you won't care whether it stands.”
I had never forgotten that.
Now I wondered what he would have thought about a woman using an official-looking notice to justify tearing down something she had never helped build.
Probably not what I was thinking.
My grandfather had a stronger temper than I did, but he also had a habit of waiting until he understood a problem before acting on it.
I returned inside and opened the folder Ellen had sent.
At the bottom of the county's response was a paragraph that I had initially overlooked.
The records office had noted that the seal on the notice resembled a generic administrative emblem rather than the county's current official seal.
That detail was not proof of misconduct. Government offices sometimes use different formatting across forms and departments, and old documents can look different from current ones.
But the county had also noted that the document's reference format did not match the numbering system used by the offices responsible for property enforcement.
The seal was merely the most visible problem.
The deeper issue was that nobody could identify an official record behind it.
I called Deputy Mendoza and provided the county's response.
She told me to forward it through the contact information on my incident report.
“I'll add it to the file,” she said. “The county will need to verify the document's origin.”
“Do you think it was fabricated?”
“I think it's suspicious enough that it needs to be checked. That's all I can responsibly tell you right now.”
I appreciated her answer.
The next morning, she called back.
She had reviewed the new material and wanted to ask several additional questions about the circumstances in which Celeste presented the notice.
I told her everything I remembered: the leather bag, the way Celeste had held the document away from me, her insistence that I had missed the deadline, and her hesitation when I asked to photograph it.
I did not embellish anything.
I did not claim to know what Celeste had been thinking.
I described what I had seen and heard.
Deputy Mendoza asked whether Celeste had ever provided a copy by email or through another formal channel.
“No.”
“Has she identified the person who served it?”
“No.”
“Has she identified the issuing officer?”
“No.”
“Has she produced a recorded easement?”
“No.”
The deputy thanked me and said she would forward the information for review.
Two days later, another development occurred.
A letter arrived from the county's administrative services office.
It stated that an initial review had found no record of the Land and Water Compliance Division issuing the notice. The county was continuing to examine whether the document had originated from another organization or had been prepared using a template not associated with an authorized agency.
The letter did not declare the document fraudulent.
It did, however, confirm that the county could not authenticate it.
Ellen forwarded the letter to the sheriff's office.
Then she sent Celeste a formal demand for the original notice and the identity of the person who had issued it.
The response came through Trevor Baines.
He said Celeste had received the notice from a third-party compliance consultant who had advised her that the access corridor was subject to restoration.
He did not identify the consultant.
He did not provide an original file.
He did not provide a service receipt.
Instead, he attached a new document: a memorandum titled Agricultural Access Compliance Summary.
It described the historical Mason lateral and asserted that the corridor had remained available for maintenance purposes.
It also stated that the notice had been prepared to facilitate compliance with the historical access obligation.
I read it twice.
The memorandum did not say that the county had issued the notice.
It did not identify a government employee.
It did not cite an actual administrative order.
It appeared to be a private document written to support Celeste's position.
Ellen called it what it was.
“A consultant's opinion,” she said. “Not proof of governmental authorization.”
“Why would they use a county-style seal?”
“That's one of the questions we need answered.”
I stared at the screen.
The memorandum was dated September 7.
The notice had been dated September 8.
The objection deadline was calculated from the supposed service date.
And the date of the alleged service was the point Celeste had used to argue that our rights had expired.
I asked Ellen whether the consultant's name appeared anywhere in the metadata.
“We're checking the electronic files. Metadata can be useful, although it must be interpreted carefully. It can be altered or lost when documents are copied.”
That afternoon, she sent a request for the original electronic version of the notice, including available file properties and transmission records.
Trevor did not respond.
A week later, the sheriff's office contacted Ellen to request another copy of the document.
They wanted the highest-quality image available, along with the original email from Trevor and the county's response.
Ellen provided everything.
Then she called me.
“The matter is now being reviewed beyond the initial property complaint,” she said. “I can't tell you what conclusion investigators will reach, but they are examining the document's origin.”
I sat quietly for several seconds.
“Does that mean Celeste is in trouble?”
“It means the document needs to be authenticated. Let's not get ahead of the evidence.”
That was difficult advice to follow.
I was angry.
I was angry that Celeste had damaged the arbor.
I was angry that she had told us we were too late to object to a notice we had never received.
I was angry that we had spent weeks digging through records while construction continued next door.
But beneath the anger was something more unsettling.
I had begun to understand how easily an official-looking document could change a person's behavior.
If I had been less willing to question Celeste, I might have accepted her explanation.
I might have assumed the county had made a mistake.
I might have paid someone to remove the arbor myself, simply to avoid a legal dispute.
I might have allowed her to proceed with the next stage of her project because she had convinced me that I had no right to object.
The document's power had never depended entirely on whether it was valid.
It depended on whether we believed it was.
That evening, Emma found me examining the remaining cedar frame.
“Dad?”
“Hey.”
She stood beside me, looking at the broken beams.
“Can we rebuild it?”
I smiled faintly.
“Yes. We're going to rebuild it.”
“Exactly the same?”
“As close as we can.”
She considered that.
“Grandpa would want it to be strong.”
“He would.”
She reached out and touched one of the old posts.
“Then we should make it stronger.”
I looked at her.
It was such a simple thing to say.
No legal theory.
No administrative procedure.
No arguments about historical maps.
Just the belief that something damaged could be repaired without pretending it had never been broken.
I put my hand on her shoulder.
“We will.”
Behind us, the lights at Rowan Fields flickered on.
The greenhouse glowed against the darkening fields. Workers were still moving near the pumping station, and the sound of machinery carried faintly across the boundary.
Celeste's project was still advancing.
Her claimed access right remained unproven.
Her notice remained unauthenticated.
And the investigation had begun.
I didn't know how it would end.
But I knew one thing with certainty.
We were no longer dealing with a simple disagreement between neighbors.
We were dealing with a claim of authority that had not survived its first serious examination.
And the more we examined it, the more important it became to determine who had created the document, why it had been presented to us, and what Celeste intended to accomplish with it.
Because the arbor was only the first thing she had tried to remove.
The Water Line Beneath Rowan Fields
The next important piece of evidence came from an engineer who had no reason to care about our grape arbor.
His name was Daniel Foster.
He worked for a consulting firm that had been engaged to review the water infrastructure associated with Rowan Fields. His role was technical, not legal. He examined proposed routes, water demand, pumping capacity, and the feasibility of connecting the project to available sources.
He contacted Ellen after receiving a request for records concerning the proposed access corridor.
“I understand that your clients own the property immediately west of Rowan Fields,” he said during a conference call.
“Yes,” Ellen replied. “What can you tell us about the proposed alignment?”
“Only what is relevant to the engineering documents I've reviewed. I don't have authority to interpret property rights.”
“That is understood.”
Daniel explained that the original water plan had considered several alternatives.
One involved using an existing well on Celeste's property, subject to capacity testing and applicable approvals.
Another involved a connection to a district-managed agricultural system.
A third considered storage and delivery arrangements that would require additional infrastructure.
The plans had evolved over time.
The current version showed a proposed connection near the eastern side of Rowan Fields, with a distribution system running toward the greenhouse and production fields.
The historical Mason lateral appeared in earlier drawings as a potential route.
But Daniel emphasized that a historical route was not the same thing as an approved, usable connection.
“The old alignment was included as a preliminary reference,” he said. “It would still require verification of the actual pipe location, condition, available capacity, and legal access.”
Ellen asked whether the proposed route crossed our property.
“In the preliminary drawings, the old alignment does. The later drawings appear to use a different route, but I would need to check the exact version and survey reference.”
“Has your firm confirmed that the old route remains available for maintenance?”
“No. That isn't an engineering conclusion we can make without the legal and title information.”
“Has your firm authorized anyone to remove structures from Mr. Trent's property?”
“Absolutely not.”
The words were clear.
Daniel had not authorized Celeste to cut the arbor.
He had not issued the notice.
He had not represented that the county had approved the corridor.
He had simply reviewed engineering alternatives.
After the call, Ellen asked him to provide copies of the relevant drawings and a statement clarifying the limits of his work.
He agreed.
A few days later, the documents arrived.
They included several versions of the water-system plan, each marked with a revision date.
The earliest version showed the historical Mason lateral crossing the approximate location of our backyard.
A later version showed a possible connection to the relocated alignment.
The most recent version contained a note beside the old route.
EXISTING RIGHTS AND PHYSICAL ALIGNMENT TO BE VERIFIED BEFORE CONSTRUCTION.
I read the note aloud to Sarah.
She looked at the drawing.
“So even their own engineer says the route hasn't been verified.”
“Yes.”
“And Celeste was already cutting the arbor.”
“Yes.”
Sarah shook her head.
“That's not just premature. It's reckless.”
I didn't disagree.
But Ellen cautioned us against drawing conclusions about the entire project from a single engineering note.
“The note establishes that verification was required,” she explained. “It doesn't establish who knew what, when they knew it, or whether someone else provided additional information.”
That distinction became important when we received another document.
It was an internal project memorandum dated September 5, three days before Celeste's notice.
The memorandum discussed delays in confirming the water connection and recommended that the project team resolve the access question before proceeding with work near the eastern boundary.
A second page referred to a possible dispute with an adjoining landowner.
The landowner was not named, but the parcel reference matched ours.
I felt a cold weight settle in my stomach.
Celeste had known there was an unresolved access question before she presented the notice.
The memorandum did not prove that she had knowingly misrepresented the situation. She might have believed the issue could be resolved through the historical records or through advice from a consultant.
But it established that the matter had not been treated as settled within the project documentation.
Ellen asked Daniel about the memorandum.
He confirmed that it was part of the project file.
He also confirmed that the engineering team had not determined that the old corridor could be used without further review.
The next question was whether Celeste had a legitimate alternative.
I asked Ellen if we could determine the current status of her well.
She said we could request public records and seek information from the relevant water authority, provided we respected any applicable privacy and procedural restrictions.
We were not entitled to demand every private financial document or internal communication simply because we were in a dispute.
But the public permits, water-system applications, and recorded agreements were fair subjects for investigation.
The records showed that Celeste had an existing domestic well.