This Could Be Your Town Next

There is a quiet conversation happening across America.

You will not hear much of it on cable news, and it probably will not dominate the next election cycle. It lives somewhere quieter than that: in county commissioner meetings, school parking lots after football games, diner booths over burnt coffee, volunteer fire halls, local Facebook groups, and conversations between neighbors standing near fences wondering what exactly is happening to the place they call home.

It often begins innocently enough. A rumor spreads about a land purchase. A developer appears. A rezoning proposal quietly enters public discussion. Someone says there is going to be a technology campus. Someone else says it has something to do with artificial intelligence. A consultant in a pressed shirt explains that there will be jobs, investment, modernization, economic revitalization, and future-proof infrastructure.

The language always sounds optimistic. Strategic investment. Innovation corridor. Economic opportunity. Regional competitiveness. Public-private partnership. Progress.

And perhaps some of those promises are even true.

But beneath the polished language and architectural renderings, something more complicated often begins unfolding, and many communities only start to recognize it after the decisions are already underway. A town that once thought of itself as farmland, forestland, ranch country, suburb, manufacturing corridor, retirement community, or simply home suddenly finds itself being discussed as an infrastructure site. Not first by the people who live there, but by people who see the map differently.

A parcel becomes capacity. A road becomes access. A river becomes cooling potential. A power corridor becomes opportunity. A quiet place becomes available.

That is when ordinary Americans are confronted with a question that sounds abstract until it lands in their own county:

Who actually gets to decide what happens to a town?

Not in theory. Not as a civics lesson. Practically.

When the roads change, when the water demands change, when the electrical load changes, when the emergency planning changes, when the identity of a community shifts, when the scale of development exceeds anything local residents ever imagined would arrive at their doorstep, who decides?

And just as importantly, who carries the consequences?

Because whether we are prepared to admit it or not, America is entering a new industrial era. Only this time, the factories often arrive without smokestacks.

The New Industrial Revolution Nobody Prepared Communities For

Let us begin with an uncomfortable truth: the future is not asking permission.

Artificial intelligence is not going away. Cloud computing is not going away. Digital infrastructure is not going away. Whether we like it or not, modern life increasingly depends on vast systems of computing power that most of us never see and rarely think about. Hospitals rely on them. Banks rely on them. Schools rely on them. Governments rely on them. Businesses rely on them. Families rely on them every time they store photos, stream a movie, send a message, use GPS, file taxes, check a medical portal, or ask a machine to summarize something they no longer have time to read.

You are likely reading this essay because a data center somewhere is quietly doing its job.

The issue, then, is not whether America needs digital infrastructure. We do.

The issue is whether our civic systems have kept pace with the scale and consequences of what is being built.

Modern hyperscale data centers, especially those designed to support artificial intelligence, are not modest warehouses filled with blinking lights. They are industrial infrastructure. They bring large-scale power demand, cooling systems, long-term land-use commitments, transmission questions, backup power systems, water considerations, emergency planning implications, tax questions, local-service burdens, and permanent physical transformation.

In some cases, these facilities are large enough to reshape the economic, environmental, and civic character of an entire region. Yet many communities are still being asked to evaluate them using assumptions built for a far simpler era.

An era before hyperscale AI. Before trillion-dollar companies quietly began reshaping the geography of American infrastructure. Before a single development proposal could carry consequences stretching decades into the future.

We are increasingly approving tomorrow’s industrial systems using yesterday’s civic playbook.

That should concern us, not because technology is bad and not because innovation is dangerous, but because scale changes responsibility. A small project can be absorbed by a community. A massive project can redefine one. A modest business can join the local fabric. A hyperscale industrial campus can alter the fabric itself.

And responsibility, in a healthy democracy, should never drift too far away from the people expected to live with the consequences.

Aside: The Scale Problem Is No Longer Theoretical

Watch: Kevin O’Leary’s data center would be the largest in the world

This short clip matters because of the scale it reveals. Whether one admires Kevin O’Leary’s ambition or recoils from the implications, the point is not really one man, one project, or one location. The point is that the conversation has already moved into a new category.

We are no longer talking only about server rooms, business parks, or ordinary industrial development. We are talking about proposals that can be described, without irony, as potentially the largest data centers in the world. That phrase should stop every serious citizen for at least a moment.

Because if this is the scale of what is being discussed publicly now, what will communities face five years from now? Ten years from now? What happens when the logic of artificial intelligence demands ever more computing power, ever more land, ever more electricity, ever more cooling, and ever faster approval?

A town can evaluate a grocery store, a warehouse, a housing development, or a factory using familiar tools. Residents may still disagree, but at least the categories are recognizable. Traffic. Jobs. Noise. Taxes. Schools. Housing. Public services. Environmental impact.

Hyperscale data centers are different. Their local footprint may serve distant users, distant companies, distant investors, and distant strategic priorities. The community hosting the infrastructure may not be the community receiving most of the benefit.

That does not automatically make the project wrong. But it does mean the burden of proof should be higher.

A development model that extracts local capacity to serve distant demand must be examined with extraordinary care. Otherwise, small communities risk becoming physical hosts for economic systems in which they hold very little power.

The Great Responsibility Drift

There is a phrase that deserves wider public attention: responsibility drift.

You may not have heard it before, but once you recognize it, you begin seeing it everywhere.

Responsibility drift happens when the benefits of a decision move upward while the burdens quietly move outward. Investment grows. Stock prices rise. Tax incentives are granted. Ribbon cuttings happen. Political speeches celebrate progress. Economic headlines sound encouraging. Consultants get paid. Developers move on to the next project.

But somewhere beneath the optimism, local communities inherit a quieter set of responsibilities that rarely make the press release.

The roads. The emergency response planning. The infrastructure strain. The water questions. The electrical load. The land-use consequences. The environmental uncertainty. The school-funding tradeoffs. The social tensions that emerge when a town suddenly feels like it is changing faster than the people living there can process.

In short, the profits often centralize while the responsibilities decentralize.

Ordinary citizens are left asking whether they were ever meaningful participants in the process to begin with.

To be clear, this is not an accusation against every developer, every policymaker, or every company involved in digital infrastructure. Many people working in this space are acting in good faith. Many genuinely believe they are helping communities modernize. Some may be. But good intentions alone do not erase the reality of unequal power.

A billion-dollar developer and a town of 4,000 people do not enter negotiations from the same position. A rural county with a part-time planning staff does not have the same resources as a multinational corporation with attorneys, lobbyists, engineers, public relations teams, tax strategists, and political relationships.

Pretending otherwise is not fairness. It is theater.

Responsibility drift is not always dramatic. It does not always arrive as corruption, villainy, or conspiracy. More often, it arrives through complexity. Through speed. Through specialized language. Through meetings scheduled when working people cannot attend. Through documents too technical for the average resident to interpret without help. Through public comment periods that satisfy legal requirements while doing little to create genuine understanding. Through the quiet exhaustion of people who have jobs, children, aging parents, bills, and not enough time to become experts in electrical grids, water rights, land-use law, tax abatements, and environmental review.

That is how a community can technically be consulted while still feeling functionally ignored.

And when people feel ignored long enough, they stop trusting the process.

This Is Not About Being Anti-Technology

It is important to say this plainly: the problem is not data centers themselves.

Data centers are part of modern life. They support medical records, emergency communications, financial systems, education, research, commerce, navigation, public services, and countless tools that ordinary people use every day. A serious society cannot simply pretend that digital infrastructure is optional.

But acknowledging need is not the same as surrendering judgment.

We need bridges, too. That does not mean any bridge should be built anywhere, by anyone, under any terms, with any public subsidy, without meaningful review. We need power plants, roads, hospitals, rail lines, and ports. That does not mean communities should be expected to accept permanent consequences without clear standards, enforceable obligations, and honest public discussion.

The question is not whether America should build the infrastructure of the future. The question is whether we will build it with civic maturity.

Can we support innovation without turning small towns into sacrifice zones? Can we welcome investment without allowing public responsibility to be quietly transferred onto residents? Can we build necessary systems without pretending that local consent is an inconvenience to be managed rather than a democratic principle to be honored?

Those are not anti-technology questions. They are pro-democracy questions.

And they matter because once massive infrastructure is approved, the balance of power often changes. Before approval, the community may still have leverage. After approval, the conversation can become narrower, more technical, more defensive, and more difficult to reverse. That is why the moment before approval matters so much.

That is the moment when citizens still have a chance to ask the questions that should have been asked at the beginning.

What are we gaining? What are we risking? Who pays for the upgrades? Who pays if projections are wrong? Who monitors water use? Who verifies power impacts? Who responds in an emergency? What happens if the company changes ownership? What happens if the project expands? What happens if the promised jobs are fewer than expected? What happens if the tax benefits do not match the public costs? What happens when the ribbon cutting is over and the cameras leave?

And perhaps the deepest question of all: who remains accountable when the people who made the deal are no longer in office, no longer employed, or no longer living anywhere near the consequences?

Aside: This Is Not a Left-Right Issue Once It Lands in a Real Town

Watch: We Took AOC To A Deep Red Data Center Town. Can She Win Residents Over?

This video is useful not because everyone will agree with Alexandria Ocasio-Cortez, the producers, the framing, or any particular political interpretation. Many will not. That is fine.

Its deeper value is that it shows something national politics often fails to understand: once an infrastructure fight becomes local, familiar partisan categories start to break down.

A conservative farmer and a progressive environmentalist may arrive at the same meeting for different reasons. One may worry about property rights, taxes, and local control. The other may worry about water, emissions, and climate impacts. A parent may worry about school funding. A firefighter may worry about emergency preparedness. A retiree may worry about noise, wells, property values, or the character of the town. A small business owner may worry about whether infrastructure costs will eventually find their way into local rates.

Different doors. Same room.

That is the part national politics often misses. Real communities are not cable news panels. They are complicated ecosystems of people who may disagree loudly on Monday and still help pull each other out of a ditch on Tuesday. They know that a town is not an ideology. It is a place. It is memory, work, weather, habit, grief, pride, argument, repair, and belonging.

When a project threatens to alter that place permanently, people deserve more than partisan slogans. They deserve tools. They deserve information. They deserve time. They deserve leverage. They deserve a process worthy of the stakes.

The ordinary American voter understands this better than most pundits do. A person may vote red, blue, independent, or not at all, but almost everyone understands the feeling of being steamrolled by people with more money and better access. Almost everyone understands the insult of being told a decision is good for them by people who will not have to live with the consequences. Almost everyone understands the difference between being consulted and being managed.

That is why this issue has the potential to create unusual alliances. It is not left versus right. It is local dignity versus distant power.

When Oversight Lags Behind Ambition

Across multiple states, communities are increasingly asking whether public oversight is keeping pace with private ambition.

Watch: Ron DeSantis Doesn’t Want You to Know About This Data Center

The title is provocative, as modern media titles often are. Set that aside for a moment. The deeper point is the same pattern visible across the country: a major project appears, public officials emphasize opportunity, residents begin asking questions, details prove more complicated than advertised, and concerns emerge about transparency, public cost, infrastructure, environmental impact, water, power, or political influence.

By the time the community fully understands what may be happening, decisions may already be advanced enough to feel difficult to stop or meaningfully reshape.

That is not how trust is built.

Trust is built when people are brought in early, spoken to plainly, given access to independent information, and treated as citizens rather than obstacles. Trust is built when public officials remember that economic development is not a substitute for democratic consent. Trust is built when developers understand that communities are not merely permitting environments. They are living places.

The lesson is simple: communities should not have to reverse-engineer accountability after the bulldozers arrive.

We should be planning before irreversible decisions happen, not after.

That is not obstruction. That is maturity.

Why “Slow Down” Is Not the Same as “No”

One of the most manipulative habits in modern public debate is the tendency to treat caution as hostility.

Ask questions and you are anti-growth. Request data and you are anti-business. Demand accountability and you are anti-progress. Propose a pause and you are standing in the way of the future.

This framing is lazy, unfair, and corrosive.

A community that says “slow down” is not necessarily saying “no.” It may be saying, “We do not yet understand the consequences.” It may be saying, “The process is moving faster than public trust.” It may be saying, “The people who live here deserve time to learn what the experts already know.” It may be saying, “We are not opposed to development, but we are opposed to being rushed into permanent decisions under temporary pressure.”

In a healthy society, that should be seen as wisdom.

A pause can be responsible. A moratorium can be prudent. A demand for independent review can be common sense. A request for stronger standards can protect both communities and reputable developers by creating clearer expectations for everyone.

The only people who should fear accountability are those relying on its absence.

Good developers should welcome clear rules. Good public officials should welcome informed citizens. Good legislation should make responsible development easier and reckless development harder.

That is not radical.

That is basic civic hygiene.

Oregon’s DCAMA as a Citizen-Led Template

This is where Oregon offers a useful example, not because Oregon has all the answers, but because citizens there are beginning to ask the right category of questions.

The proposed Data Center Accountability & Moratorium Act, or DCAMA, is not merely a technical policy idea. At its best, it represents something deeper: a citizen-led effort to restore proportion between industrial ambition and public accountability.

No proposal is perfect. Any serious bill should be reviewed, debated, amended, stress-tested, improved, and adapted to real legal and economic conditions. But the basic spirit behind DCAMA deserves attention from communities far beyond Oregon.

That spirit is simple: before massive data center expansion continues unchecked, communities deserve transparency, enforceable standards, and the right to understand what they are being asked to host.

The current Oregon draft recognizes that the strongest path is not an indefinite anti-technology ban, but a narrower, defensible, time-limited moratorium tied to findings, agency rulemaking, fiscal accountability, and cost-allocation obligations. In plain English, that means: pause long enough to understand the consequences, write rules that match the scale of the problem, and make sure the people creating the burden pay for the burden.

That matters because the public is often told to trust the promise of economic development while being denied a full accounting of public costs. The DCAMA draft flips that assumption. It begins from a simple civic principle: if a covered data center imposes costs on electric ratepayers, water systems, wastewater systems, roads, emergency services, schools, environmental quality, or future cleanup, those costs should not quietly drift onto ordinary residents.

The draft’s central concept is a “pay your way” framework. That phrase is plain enough for a town hall and serious enough for statutory language. It means covered operators should pay for prevention, operation, infrastructure impacts, monitoring, decommissioning, and remediation. It means lifecycle accountability, not just ribbon-cutting promises. It means costs should not be shifted to residential customers, small businesses, schools, or taxpayers who never consented to subsidize the back end of someone else’s growth.

That is the kind of idea communities across the country can adapt.

A Florida version might emphasize local water protection, hurricane resilience, wetlands, and transparency around political approval. A Georgia version might focus on groundwater, rural wells, tax abatements, and school impacts. A Virginia version might address grid congestion, land-use saturation, and cumulative regional burden. An Arizona version might center water scarcity. A Texas version might focus on grid reliability and emergency response. A Midwestern version might focus on farmland, transmission, tax diversion, and rural infrastructure.

The details will differ. The principle should not.

No community should be forced to reinvent the wheel while facing a billion-dollar proposal under deadline pressure. DCAMA gives citizens language. It gives local leaders a starting point. It gives residents a way to move from fear and frustration into structured civic demand.

It says: we are not helpless, and we are not irrational. We are asking for standards equal to the scale of what is coming.

What Sensible Accountability Could Look Like

A serious data center accountability framework should begin with transparency. Communities deserve plain-language disclosures about projected water use, power demand, backup generation, expected emissions, tax arrangements, infrastructure upgrades, emergency response needs, noise impacts, land-use changes, and expansion possibilities.

Not vague assurances. Not glossy summaries. Not “trust us” language.

Actual information.

Second, communities deserve independent analysis. A developer-funded report is not the same as independent public review. Expertise matters, but so does who pays for it, who frames the questions, who controls the assumptions, and who gets access to the findings. Local governments should not be forced to rely primarily on information prepared by the very parties seeking approval.

Third, infrastructure costs must be clearly assigned. If roads must be upgraded, substations expanded, transmission lines modified, emergency systems improved, or public services expanded, residents deserve to know who pays. A project that looks profitable on paper may become far less attractive if the public quietly absorbs the support costs.

Fourth, water and power impacts must be treated as central questions, not technical footnotes. In many regions, water is not an abstraction. It is agriculture, fish, wells, ecosystems, fire resilience, household security, and future growth. Electricity is not just a commodity. It is grid reliability, ratepayer burden, industrial capacity, household affordability, and public resilience. Communities deserve to understand whether a project strengthens or strains these systems.

Fifth, emergency preparedness must be real. Large industrial facilities bring risks that small communities may not be equipped to manage without additional training, equipment, staffing, and funding. If a facility requires specialized response capacity, that capacity should not become an unfunded mandate on local fire departments, emergency managers, or taxpayers.

Sixth, public participation must be meaningful. A meeting held after key decisions have effectively been made is not consent. A three-minute comment period is not deliberation. A technical document dumped online is not transparency. Communities need early notice, accessible explanations, multiple opportunities for engagement, and enough time to organize, learn, and respond.

Seventh, accountability must outlive the approval process. Promises made during development should be enforceable after construction. If a company commits to jobs, mitigation, environmental performance, infrastructure funding, or community benefits, those commitments should not evaporate once permits are secured.

Finally, communities should consider whether certain projects require a temporary moratorium until standards are in place. This is not extreme. It is often the only responsible option when technology, scale, and public understanding are moving faster than the rules designed to govern them.

A moratorium is not a panic button. It is a civic seatbelt.

The Human Cost of Being Rushed

Policy arguments matter, but they can become sterile if we forget what this feels like on the ground.

Imagine being a resident in a small town where life is already complicated enough. You work. You pay taxes. You worry about groceries, healthcare, your kids, your parents, your mortgage, your rent, your animals, your job, your truck, your land, your retirement, your marriage, your back pain, your heating bill, your future.

Then suddenly you are expected to understand a complex industrial proposal with implications for water, electricity, land use, tax policy, emergency management, environmental regulation, corporate structure, and long-term regional planning.

You attend a meeting after work. The room is tense. The presentation is polished. The language is technical. Some people sound angry. Some sound confused. Some sound excited. Some sound resigned. A few officials appear impatient, as if public concern is an unfortunate stage of the approval process.

You go home with more questions than answers.

You search online. You find conflicting claims. Supporters say the project will bring jobs and revenue. Opponents say it will drain resources and change the town forever. Experts disagree. Consultants reassure. Activists warn. Officials hedge. The developer smiles.

Meanwhile, the timeline keeps moving.

This is the emotional burden rarely discussed in economic development language. Responsibility drift is not only financial or environmental. It is psychological. It forces ordinary people to become watchdogs, researchers, organizers, advocates, and amateur policy analysts just to protect the baseline dignity of being heard.

That burden is real.

And it is unfair to pretend that communities are being unreasonable when they struggle under it.

The False Promise of “Jobs” Without Context

Nearly every major development proposal arrives with the promise of jobs. Jobs are important. In many communities, they are desperately needed. No serious person should dismiss that.

But the word “jobs” should not end the conversation. It should begin one.

How many jobs? What kind? Construction or permanent? Local or imported? Living wage or specialized technical positions requiring outside hires? How many workers will actually live in the community? Will the project increase housing pressure? Will local schools benefit? Will small businesses see sustained gains or only temporary construction traffic? Will tax arrangements reduce the public upside? Will automation limit long-term employment?

A project can be large without being labor-intensive. A facility can represent massive capital investment while creating relatively few permanent local jobs. That does not make it worthless, but it does mean the public deserves a clear-eyed cost-benefit analysis rather than a slogan.

Jobs matter.

So do water, power, taxes, roads, emergency services, land, trust, and self-determination.

A healthy community should not be forced to trade away one form of survival for another without a full accounting.

Your Town Is Not an Empty Space

One of the quiet injuries in these debates is the way outside interests sometimes describe small communities as if they are empty or underused until capital arrives.

Rural land becomes available land. Small towns become low-cost markets. Communities become strategic locations. Open space becomes development opportunity. A place with memory becomes a site.

This language may be normal in business, but residents hear something else. They hear that what already exists is invisible.

The old family farm. The hunting ground. The aquifer. The two-lane road. The church supper. The night sky. The quiet. The school fundraiser. The cemetery where three generations are buried. The little hardware store. The bend in the creek. The volunteer fire department. The porch where somebody’s grandfather drank coffee every morning for forty years.

None of that appears on a corporate spreadsheet in its true value.

But it is value.

Not sentimental value as a consolation prize. Real value.

A nation that forgets this will eventually become very efficient at destroying things it does not know how to measure.

One Rising Tide

This conversation cannot become town versus town, state versus state, neighbor versus neighbor.

That road goes nowhere.

If one community is ignored, every community becomes more vulnerable. If one town is rushed into a bad deal, another town can learn from it. If one county develops stronger standards, another county can adapt them. If one state proposes a serious accountability framework, other states can improve it.

That is the One Rising Tide philosophy.

Not a rising tide of outrage for its own sake. Not a rising tide of fear. Not a rising tide of reflexive opposition to anything new.

A rising tide of civic awareness.

A rising tide of ordinary people comparing notes.

A rising tide of local officials learning from one another before mistakes become permanent.

A rising tide of citizens saying, calmly and firmly, “Before we sign away something that cannot easily be undone, we intend to understand what we are agreeing to.”

That is not fear.

That is stewardship.

America does not need every town to fight alone. We need communities to become wiser together. We need citizens in Oregon learning from citizens in Virginia, Georgia, Texas, Iowa, Arizona, Florida, and everywhere else this issue emerges. We need rural conservatives, suburban independents, environmental advocates, fiscal watchdogs, farmers, ratepayers, firefighters, parents, teachers, school-board members, and local business owners to recognize that they may have more in common on this issue than national politics would have them believe.

The future will be built somewhere. The question is whether the people living in those somewheres will have a meaningful voice.

Before It Happens to Your Town

Maybe none of this ever reaches your doorstep.

Maybe your town never sees a hyperscale data center proposal. Maybe the nearest one is hundreds of miles away. Maybe this issue feels distant, technical, or somebody else’s problem.

Until one day it is not.

Until a rumor starts. Until a land deal appears. Until a rezoning notice arrives. Until a neighbor forwards a meeting agenda. Until somebody says, “Did you hear what they’re planning out by the highway?” Until a consultant tells your county that this is an opportunity too important to miss.

That is why the time to think about accountability is before the pressure arrives.

Once a project is on the table, the timeline often belongs to someone else. The developer has a schedule. Investors have expectations. Officials have incentives. Consultants have deliverables. The public has confusion.

Preparation is the only way ordinary citizens regain leverage.

That preparation does not have to begin with opposition. It can begin with questions. Better questions. Shared questions. Questions every community should have ready before the glossy presentation arrives.

What is the total projected water use?

What is the source of that water?

What happens during drought?

What is the projected power demand?

Will new transmission be required?

Who pays for infrastructure upgrades?

Are there tax abatements or subsidies?

How many permanent local jobs will be created?

What emergency response capabilities are required?

Who funds them?

What backup power systems will be used?

What emissions, noise, or environmental impacts are expected?

Can the facility expand later without renewed review?

What happens if ownership changes?

What commitments are enforceable?

What public benefits are guaranteed?

What are the exit obligations if the facility closes?

What independent review has been conducted?

What are residents not being told because nobody has asked yet?

Those questions are not hostile. They are responsible.

A developer worthy of public trust should be able to answer them.

A public official worthy of public office should want them answered.

We the People Still Means Something

The deeper issue here is not only data centers. It is whether ordinary people still believe they have the right to shape the places they live.

That belief has been weakened in America. Many citizens feel decisions are made before they arrive, that public hearings are rituals, that experts talk down to them, that corporations have access they do not, that political systems respond faster to money than to memory, faster to pressure than to place.

When people feel that way long enough, democracy becomes brittle.

The data center boom is therefore more than a land-use question. It is a test of whether local democracy can still function under the weight of modern capital and technological urgency.

Can a small town ask a billion-dollar question and get an honest answer?

Can a county say, “We need more time,” without being labeled backward?

Can citizens demand accountability without being dismissed as emotional, ignorant, partisan, or anti-progress?

Can public officials remember that their first obligation is not to the deal, the headline, the developer, the party, or the next office, but to the people who must live with the outcome?

If the answer is yes, then we still have something worth building on.

If the answer is no, then the problem is much larger than data centers.

A Better Way Forward

America does not need to choose between innovation and community dignity.

That is a false choice.

We can build data centers and require transparency. We can support digital infrastructure and protect water. We can welcome investment and demand enforceable commitments. We can create jobs and still ask whether public costs are being hidden. We can move toward the future without treating local people as collateral damage.

But doing so requires a better civic posture than passive acceptance.

It requires citizens willing to learn. Officials willing to slow down. Developers willing to be transparent. Legislators willing to act before harm becomes obvious. Journalists willing to dig. Neighbors willing to talk across political lines. Communities willing to insist that scale, speed, and complexity are not excuses for weakened democracy.

The Oregon DCAMA draft is one possible starting point. Not the final word. Not a perfect model. Not a magic shield. But a serious citizen effort pointing in the right direction.

Other communities should study it, challenge it, improve it, adapt it, and demand their own versions where needed. Let Oregon’s effort become part of a larger national conversation about what responsible digital infrastructure should look like in a free society.

A society worthy of the name does not build the future by exhausting the people asked to host it.

It builds the future by including them.

Home Deserves a Voice

In the end, this is about more than servers, tax incentives, water use, power demand, or zoning.

It is about home.

That word may sound too simple for a policy debate, but it is the truest word we have. Home is where abstractions become personal. It is where infrastructure becomes traffic on your road, water from your well, noise beyond your fence, taxes in your mailbox, lights on your horizon, and decisions your grandchildren may inherit.

Home is not a blank space waiting for a better use.

Home is already a use.

A sacred one, even when it is ordinary. Especially when it is ordinary.

The future does not belong only to billionaires, lobbyists, corporations, consultants, or politicians. It also belongs to the people who wake up every morning and call a place home. The people who fix the roads, teach the children, answer the emergency calls, run the diners, cut the hay, stock the shelves, coach the teams, tend the gardens, bury the dead, and keep showing up long after the press conference ends.

Those people deserve a voice.

Not after the deal is done.

Not after the permits are issued.

Not after the land is cleared.

Before.

Before the promise becomes pressure. Before the pressure becomes inevitability. Before inevitability becomes regret.

This could be your town next.

And if it is, may you have more than rumor, confusion, and a three-minute comment period standing between your community and a decision that could shape generations.

May you have information.

May you have time.

May you have neighbors who refuse to be divided.

May you have public servants who remember the meaning of service.

May you have laws strong enough to match the scale of what is coming.

And may you remember, before anyone convinces you otherwise, that “We the People” was never meant to be decorative language.

It was meant to be a warning.

A promise.

And a responsibility.

The future is coming.

Let it come with consent.

Let it come with accountability.

Let it come with wisdom.

And let it never again be said that ordinary Americans were too distracted, too divided, too tired, or too intimidated to defend the places they love.

Appendix: Draft Oregon DCAMA Model Language

The following draft language is included as a working citizen-legislation model. It is not final legal text and should be reviewed, revised, and adapted by qualified legislative counsel, local officials, policy experts, affected communities, and citizens before use. Its value here is not perfection. Its value is that it gives ordinary people a serious starting point.

Findings and Purpose

“The Legislative Assembly finds that high-impact data centers may impose substantial costs on electric ratepayers, water resources, public infrastructure, school funding, land use, and environmental quality; that existing Oregon law does not yet ensure full lifecycle accountability for those costs; and that a temporary moratorium and accountability framework are necessary to protect the public interest while state agencies adopt uniform standards.”

Definitions

“‘Covered data center’ means a new or expanded facility, campus, or integrated project used primarily for computing infrastructure, data processing, web hosting, artificial intelligence model training, cloud operations, colocation, blockchain operations, or related digital services that: (a) uses or is capable of using 20 megawatts or more of electricity; (b) withdraws, consumes, stores, or discharges water above a threshold established by rule; or (c) operates standby generation above a threshold established by rule.”

Moratorium

“A state agency, local government, municipal corporation, or political subdivision may not, during the moratorium period, approve, authorize, certify, or materially amend a permit, land-use approval, tax incentive, utility-service commitment, water-right approval, or other governmental authorization for a covered data center, except as expressly provided in this Act.”

Joint Study and Rulemaking

“No later than 12 months after the effective date of this Act, the Department of Energy, the Public Utility Commission, the Water Resources Department, the Department of Environmental Quality, the Department of Land Conservation and Development, and the Oregon Business Development Department shall jointly submit to the Legislative Assembly a report and proposed rules addressing cumulative electric, water, wastewater, air-emissions, land-use, fiscal, labor, and school-funding impacts of covered data centers.”

Post-Moratorium Approval Standard

“After expiration of the moratorium, a covered data center may not receive a state or local approval unless the applicant demonstrates through substantial evidence that the project will not cause unwarranted cost shifting to other utility customers, will not impair existing water-right holders or instream values, will not reduce local public-service capacity without full mitigation, and will satisfy all accountability requirements established under this Act and rules adopted under this Act.”

Full Lifecycle Cost Allocation

“A covered data center shall bear all reasonably attributable costs for prevention, operation, monitoring, closure, decommissioning, environmental remediation, public-infrastructure upgrades, grid extensions, transmission or distribution enhancements, water and wastewater facilities, transportation access, emergency-response planning, and post-closure site restoration, and no such costs may be shifted to residential, small-business, or nonparticipating public customers except as expressly authorized by statute.”

Zero-Impact Cooling Standard

“A new covered data center may not use once-through cooling and must employ closed-loop, non-evaporative, or functionally equivalent cooling technology that demonstrates no net adverse impact on local water supply, groundwater levels, streamflow, wastewater capacity, or water quality, as determined under standards adopted jointly by the Water Resources Department and the Department of Environmental Quality.”

Tax-Abatement Disqualification and School Protection

“Notwithstanding any other provision of law, property used in operating a covered data center is ineligible for exemption or special treatment under the Strategic Investment Program, the standard enterprise-zone program, and the long-term rural enterprise-zone program. The State Treasurer shall establish a Data Center Accountability Fund, and moneys in the fund shall be used first to replace verified school-funding losses and agency implementation costs attributable to covered data centers.”

Financial Assurance and Remediation

“Before any post-moratorium approval takes effect, the applicant shall provide financial assurance in a form approved by rule and in an amount sufficient to cover monitoring, emergency response, infrastructure retirement, closure, decommissioning, contaminated-water response, solid and hazardous waste management, and site remediation for the covered data center.”

Transparency and Quarterly Reporting

“Each covered data center shall report quarterly to the Department of Energy and the Water Resources Department its electricity demand and consumption, water withdrawals and consumption, wastewater volumes, standby-generator operations, onsite fuel use, greenhouse-gas and criteria-pollutant emissions, employment, tax-abatement activity, and community-benefit payments; the agencies shall publish nonconfidential summaries in a searchable online format.”

Enforcement and Penalties

“A person that violates this Act, a rule adopted under this Act, or a condition of approval issued under this Act is subject to civil penalties, injunctive relief, permit suspension or revocation, disqualification from any state or local tax incentive, and recovery by the state or affected local governments of public costs incurred because of the violation.”

Grandfathering and Transition

“This Act applies prospectively to applications not finally approved before the effective date of this Act. A project with a vested land-use right or final permit may proceed only to the extent of the vested approval, but no expansion, amendment, new tax incentive, or new utility-service commitment for additional capacity may be approved unless the project complies with this Act.”

The Plain-English Demand

A community does not need to become anti-technology to demand this kind of framework.

It only needs to become serious.

Ordinary customers should not bankroll data-center power infrastructure. Schoolchildren should not lose tax base so that hyperscale facilities can receive abatements. Communities should not lose water capacity, wastewater capacity, road capacity, or emergency-service capacity without full mitigation. And the public should never be left holding the cleanup bill after the operator extracts the gains.

That is the heart of the matter.

We already pay for enough.

We should not have to pay twice for someone else’s future.