For years, I had imagined that protecting Blue Heron meant standing between it and whatever threatened to erase it. Now I understood that protection also meant making the record strong enough to outlast my attention. Someone else would take the next reading. Someone else would question the next plan. Someone else would notice when the water moved in a direction the map did not expect.
That was how a place became more than a cause. It became part of the way a community understood itself.
I stepped onto the porch. Morning light spread across the pond, touching the reeds one by one. The water held the sky without holding it still. And for the first time in a long while, I let myself enjoy the view without wondering what letter might arrive next.
Three months after I wrote that final entry, the county sent a notice about a proposed change to its stormwater fee schedule. The notice was ordinary, printed in black type and mailed with the utility bills. Most people would have read the first paragraph, noticed the new amount, and set it aside. I read the attachment because the phrase “regional detention capacity” caught my eye.
The county was considering a program that would allow large developments to receive credits for maintaining private stormwater facilities. On paper, the idea made sense. If a property owner built and maintained a basin that reduced runoff, the county could recognize that work rather than require the same capacity elsewhere. But the draft language treated every facility as if it served only the parcel where it stood.
Blue Heron was not a private detention basin. It was part of a connected wetland system, and its value could not be measured only by the volume of water it held after a storm. The distinction was easy to miss in a spreadsheet.
I forwarded the notice to Mara. Her reply came ten minutes later: “We should read the definitions before we panic.”
I smiled at the screen. Three years earlier, I would have started with the panic.
The definitions were worse than the headline. The draft allowed a developer to claim credits for a facility if it met specified storage and maintenance standards. It did not clearly distinguish engineered detention ponds from natural wetlands, nor did it explain how credits would be calculated when a water feature served a broader watershed.
The county's public comment period lasted forty-five days. We had time, but not unlimited time. Mara proposed that we prepare a technical comment rather than a protest letter. The watershed district agreed to review our concerns, and the county engineer offered to explain the draft methodology.
At the library, we spread the documents across two tables. Mateo, now more confident with the gauges, read the definitions aloud while Jasmine marked every reference to ownership and maintenance. Paul checked the fee schedule. Denise compared the proposal with the HOA's existing obligations.
We found that the draft could unintentionally reward a property owner for preserving a wetland while also allowing that same wetland to be counted as a substitute for infrastructure elsewhere. The result might be a double benefit: a credit for the landowner and an assumption by the county that the watershed had gained storage capacity that was already part of its natural function.
“We need to be precise,” Mara said. “We're not against credits. We're against counting the same service twice.”
That became the center of our comment.
I drafted the first version and sent it to the committee. It was too long. Alvarez crossed out three paragraphs and wrote in the margin, “Show the consequence before the terminology.” The county engineer suggested a simple diagram. The district hydrologist provided language distinguishing natural floodplain storage from constructed detention volume.
We revised the document until it fit on six pages, with an appendix containing the maps and monitoring data. The opening example described a heavy rainfall event in which water moved from the upper basin through the western swale, spread across the meadow, and reached the lower marsh. The diagram showed how a change at one point could affect the timing and volume of flow downstream.
I read the final draft aloud at the committee meeting. Nobody objected to the technical language, but Paul raised a concern.
“Will ordinary residents understand why this matters?”
“Maybe not every calculation,” I said. “But they should understand the basic point: a wetland isn't an empty tank waiting to be assigned to whoever owns the nearest lot.”
Jasmine suggested a one-page summary with three questions: What is being measured? Who benefits? What happens downstream? We added it to the packet.