Desk Setup
Treat Environment Like A Real Desk
This desk is where wetlands, floodplain, fisheries, habitat loss, permits, levees, spills, and downstream public-risk stories should live together instead of being stranded in the general story feed.
Environment Desk
Environment
This issue file is where environmental reporting should connect back to the source record: permits, agency reviews, water systems, habitat, infrastructure, and downstream public exposure. Stories still publish in the main feed, but the desk should hold the file and the latest linked reporting.
Desk Setup
Follow Records, Not Vibes
The strongest environmental reporting here is not generic climate copy. It is local record work tied to permits, agencies, land-use fights, water systems, and infrastructure risk.
Desk Setup
One Cluster Should Not Own The Desk
Port Westward is the clearest active file right now, but the desk should stay wide enough for land, habitat, water, industrial siting, and public-exposure stories elsewhere too.
What Belongs Here
Use the desk to hold the file, then let stories do the readable reporting
Issue files should hold the framing and the source lanes. The story feed can stay fast, but every environmental story should still roll back into a desk the reader can follow.
Permits + Water
Wetlands, fill permits, 401 certifications, and federal environmental review files show where the public record starts.
Infrastructure + Exposure
Levees, drainage districts, roads, spill response, port infrastructure, and public repair bills show who absorbs risk when projects go sideways.
Habitat + Downstream Impact
Fisheries, habitat, tribal consultation, navigation, and downstream-use records show whether harm stops at the fence line or moves through a whole region.
Latest From This File
Linked reporting for Environment
Stories stay in the main feed, but they should also land back on the issue file they belong to. This desk currently has 16 linked stories.
Publishing Logic
The Desk Holds The File
Use the story feed for the running report. Use the issue file to keep the source trail, the framing, and the latest linked coverage in one place.
Open the full story feed.
Last standards review: March 31, 2026
EnvironmentApril 8, 2026
Port Westward File
Port Westward Already Has A Conflict-Waiver And Rent-Relief Record
The strongest claim is not that every one of these actions was unlawful. It is that the Port Westward file already contains formal conflict optics and public-risk sharing that deserve far more scrutiny than a routine industrial project would.
Port WestwardNEXT Renewable Fuels
Records Research Desk • 6 min read
Read Story
EnvironmentApril 8, 2026
Port Westward File
The Port Westward Influence Map Runs Through Public And Private Hands
The careful claim is not that every one of these links is corrupt. It is that the Port Westward record is no longer anonymous. The same public officials, state coordinators, and developer-side names keep appearing across the lease, the board minutes, and the permitting machinery.
Port WestwardNEXT Renewable Fuels
Records Research Desk • 7 min read
Read Story
EnvironmentApril 8, 2026
Port Westward File
Port Westward Already Sits In A Tribal And Fisheries Record
The careful claim is not that every tribe has taken the same public position. It is that the official review already places this project inside a real Columbia fisheries and tribal-consultation record, not just a local zoning debate.
Port WestwardNEXT Renewable Fuels
Records Research Desk • 6 min read
Read Story
EnvironmentApril 8, 2026
Port Westward File
Port Westward Kept Moving Because Each Setback Landed In A Different Agency Lane
The tight claim is not that every agency was captured. It is that the project persisted because no single review lane carried the whole burden at once, which helps explain why locals keep saying the Port Westward record feels fragmented.
Port WestwardNEXT Renewable Fuels
Records Research Desk • 6 min read
Read Story