The river does not stop being a shared system just because the project sits on the Oregon bank
The cleanest correction to make is this: the Port Westward review is not only an Oregon story. Washington Ecology's own water-quality standards say Washington protects domestic water supply, industrial water supply, agricultural water supply, stock watering, wildlife habitat, fish harvesting, commerce and navigation, boating, and aesthetic values in its waters.
That matters because the Columbia is a shared border river, and both states treat it as more than an industrial channel.
Washington's Columbia programs are built around water for communities, farms, and industry
Washington Ecology's Office of Columbia River says its work exists to meet water needs for communities, farms, and the environment, and it says communities up and down the Columbia River system rely on that water. The agency's Columbia Basin project pages also say the state is working to make water available for municipal, domestic, industrial, and irrigation needs.
That matters because it places the Washington side squarely inside the same water-use picture: households, farm operations, industry, and fish all depend on the Columbia system remaining usable.
The state's own water-right rules show how directly Washington can depend on the river itself
Washington Ecology's Lake Roosevelt water-right page says new diversions from the Columbia can be available from wells within a mile of either side of the river along the covered corridor. That page is about a different Columbia water-right program, but the point is simple and important: Washington's own framework recognizes cross-river dependence on the Columbia water source itself.
That matters because it undercuts any idea that Oregon-side industrial risk automatically stays on the Oregon side.
The farm and food-chain issue is real because the site is tied into irrigation-support waterways
NOAA says the project area includes about 10,000 linear feet of waterways that drain floodwater and supply irrigation water to farms through McLean and Beaver sloughs. That means the local site is already connected to agricultural water management, not isolated from it.
So when people ask about food-chain or farm exposure, the strongest source-backed framing is this: the project sits in a shared river-and-drainage system that already supports farm operations and broader river uses, which is exactly why water-quality review matters.
Ports and navigation on both sides are part of the same corridor story
Washington treats commerce and navigation as designated uses, and Oregon does too. The Corps says the NEXT project could add up to 171 ocean-going vessel movements a year through the existing Port of Columbia dock.
That matters because this is not only a wetlands issue and not only a farm-water issue. It is also a navigation-corridor issue in a shared interstate river system.
What this story does and does not claim
I am not claiming I have already mapped every specific Washington city, every drinking-water intake, every ranch withdrawal, or every port operation that could be touched by a contamination event. The public documents I reviewed do not provide that complete intake-by-intake map.
What they do provide is enough to say this clearly: Washington's side of the Columbia has legally protected domestic, agricultural, industrial, livestock, fish, and navigation interests in the same river system, so the Port Westward risk story cannot honestly be kept on the Oregon side alone.
