BS Summary: This article contains 27 faulty reasoning types, including Availability Heuristic, Ambiguity (Equivocation), and Confirmation Bias, with Negativity Bias as the most egregious example at 14.8% saturation with 193 hits. Analysis detected 1,495 faulty-reasoning hits from 1,300 analyzed words, generating a BS Score of 25.2% and a BS Rank of 17% (25,374 of 30,461 articles). This article is better (less manipulative) than 83.30% of the article peer group.

Lyon County commissioners voted 3-1 Thursday to approve a zoning change needed to build the massive Monarch Data Center near Yerington, clearing a hurdle for a data center development even as many other jurisdictions in the state look to pause or re-assess data center buildout. 
Reno, Nye County and Humboldt County have all passed moratoriums on new data center approvals this year, while Clark County, Churchill County and the cities of Sparks and Fernley are weighing code changes of their own. 
But Lyon County is taking a different approach, continuing to move Monarch through its approval process even as it works separately on its own countywide rules for the industry. 
Read more: How has your city or county regulated data centers? 
Here's the latest in Nevada. 
Commissioner Dave Hockaday cast the dissenting vote and Commissioner John Cassinelli  who cited a potential conflict given his role with an economic development authority  abstained. 
Copia Power proposed the 4.6 million-square-foot, 1,000-megawatt data center campus be built on roughly 505 acres in Mason Valley. 
The project also includes a 500-megawatt natural gas backup plant and battery energy storage system. 
Conceptual two-story building dimensions for Monarch Data Center, submitted by Copia Power. 
Dozens of residents spoke against the project during the meeting, continuing a pattern of opposition present at every stage of the approval process. 
A smaller group of building-trades and business representatives urged commissioners to approve it for the jobs and tax revenue it would bring. 
Thursday's approval is only tentative. 
Copia still has to bring a final design back to the board before construction can begin, and the project still needs separate state approvals, including from the Nevada Division of Environmental Protection and the State Engineer. 
Copia also needs to complete its purchase of the land. 
Copia did not respond to a request for comment. 
Read more: No land? 
No problem: Why many Nevada data centers don't own the land they're asking to develop 
The vote follows a December vote by the board changing the site's land-use designation from "agriculture" to "specific plan"  the step required before a zone change could be sought  after tabling it in August 2025 over concerns about the project's primary access road. 
The Lyon County Planning Commission recommended the zone change, from rural residential to a planned unit development, in early July. 
Copia's presentation was led by Jeff Page, a longtime Mason Valley resident and former county manager who was retained by Copia to research the company and speak with other communities where it has built. 
During board discussion, Hockaday  the lone no vote  said the vast majority of findings in development documents prepared by county staff seemed to be framed as positive when, in his reading, most of them cut against the project, including the finding on whether the design adequately serves public services, traffic and community enjoyment. 
"I don't see any positives in the other ones," he said. 
Commissioner Robert Jacobson flagged a discrepancy on water use, noting Copia's application materials estimate total water consumption, across all uses, at under 100 acre-feet per year, while the staff report separately cites a figure of under 800 acre-feet per year, a 60 percent reduction from current agricultural use on the site. 
Both describe the same air-cooled, closed-loop system. 
Cullen McGinnis, volunteer engagement coordinator for the Sierra Club's Toiyabe Chapter, raised a related concern during public comment. 
He said Copia has been vague about exactly when its cooling system would shift toward more water-intensive operation and hasn't specified a temperature threshold for doing so. 
The staff report describes the system as not being "entirely" air-cooled, without elaborating further. 
Commissioners also pressed on power supply. 
Hockaday asked how NV Energy could provide the full 1,000 megawatts Monarch has requested, noting other companies in the region have reportedly been told they can't get service until 2032. 
A Copia representative pointed to NV Energy's most recent integrated resource plan, filed with state regulators in April. 
The representative said it commits the utility to supplying 2,550 megawatts to data centers over the next several years. 
Until Monarch's share of that capacity comes online, the company would self-supply power through its own gas plant and battery storage, phasing in the data center's buildout as grid integration happens. 
Chair Scott Keller asked whether the gas plant, initially described as backup power only, would end up running continuously once connected. 
Copia said it could run 24/7, though it usually wouldn't. 
Page has also worked with Lyon County commissioners, on behalf of Copia and EDF Winston Solar, regarding the county's renewable energy ordinance, according to county emails obtained through a public records request. 
That ordinance, passed in June 2025, set standards including setback requirements for solar and battery storage facilities in the county, while also adding a board-discretionary exception that allowed those setbacks to be reduced for planned unit development projects. 
A mockup of planned boundaries for the Monarch Data Center in Lyon County. 
Opposition and support 
Opposition centered on tribal consultation and the site's location. 
The Walker River Paiute and Yerington Paiute tribes have passed formal resolutions opposing the project, according to the Sierra Club's Toiyabe Chapter, which said afterward it believes Monarch may be the first data center proposed in Nevada to rely primarily on groundwater in an already over-appropriated basin. 
The chapter said in a statement it would "pursue every available legal avenue" to challenge the project going forward. 
Other residents raised a wider range of technical and practical objections: the potential for waste heat  heat vented off the buildings as a byproduct of cooling the servers, which some worried could raise nearby temperatures and stress irrigation and fire risk  seismic and soil-liquefaction risk on the site, traffic during construction, and health effects from noise and air emissions. 
Several speakers argued inconsistencies in Copia's presentation undermined public trust in the project. 
On the other side, Eloy Jara, business manager for Laborers' Local 169, said the project would bring significant construction work to the area. 
Kris Thompson, a former project manager at the Tahoe Reno Industrial Center in Storey County, told commissioners comparable data center campuses there generated millions of dollars a year in property tax revenue even after abatements. 
Broader data center rules for Lyon County 
Thursday's vote comes three days after the county held a workshop on its first data center-specific ordinance. 
As drafted, the ordinance would apply to new construction, major expansions of existing data centers, and conversions of existing buildings. 
Local outlets have reported the ordinance would not apply to Monarch because its application process was already underway. 
The Indy has not independently confirmed that with the county, which had not responded as of publication. 
Commissioners weren't satisfied with several of the draft's standards as written. 
Hockaday called the draft's 150-foot residential setback "absolutely unacceptable" at the workshop, comparing it to the county's solar ordinance's half-mile requirement, and argued data center setbacks should be doubled or tripled. 
Cassinelli had separately pushed back on the ordinance's water-cooling language at the workshop, calling a "prohibited... but conditionally allowed" framing contradictory and proposing an annual water-consumption cap instead. 
NV Energy Vice President Jeff Brigger told commissioners at the workshop that the utility has requests for roughly 22,000 megawatts of new demand statewide, most of it from data centers, against a 2025 peak demand of about 8,500 megawatts. 
He said a proposed cost-allocation framework would shift infrastructure costs onto large customers rather than existing ratepayers. 
The board voted unanimously to send the draft back to staff for revisions, directing increased residential setbacks, revised water and cooling provisions and clearer guidance on the Nevada Division of Environmental Protection's role in air quality permitting. 
No date has been set for the revised draft to return. 
Article reasoning-pattern comparisonThis article: 8.7%Piper Heath: 2.1%The Nevada Independent: 2.1%Confirmation Bias8.7%This article: 2.4%Piper Heath: 1.2%The Nevada Independent: 0.8%Anchoring Bias2.4%This article: 11.6%Piper Heath: 3.2%The Nevada Independent: 1.8%Availability Heuristic11.6%This article: 1.4%Piper Heath: 0.6%The Nevada Independent: 0.6%Representativeness Heuristic1.4%This article: 0.0%Piper Heath: 0.9%The Nevada Independent: 0.4%Hindsight Bias0.0%This article: 0.8%Piper Heath: 0.5%The Nevada Independent: 0.7%Overconfidence Bias0.8%This article: 3.4%Piper Heath: 5.0%The Nevada Independent: 4.4%Framing Effect3.4%This article: 0.0%Piper Heath: 2.0%The Nevada Independent: 0.6%Loss Aversion0.0%This article: 5.2%Piper Heath: 0.7%The Nevada Independent: 0.5%Status Quo Bias5.2%This article: 0.0%Piper Heath: 0.2%The Nevada Independent: 0.2%Sunk Cost Effect0.0%This article: 4.9%Piper Heath: 2.1%The Nevada Independent: 2.3%Optimism Bias4.9%This article: 0.8%Piper Heath: 2.9%The Nevada Independent: 1.5%Pessimism Bias0.8%This article: 14.8%Piper Heath: 5.1%The Nevada Independent: 4.2%Negativity Bias14.8%This article: 1.8%Piper Heath: 3.8%The Nevada Independent: 2.0%Self-Serving Bias1.8%This article: 2.1%Piper Heath: 0.5%The Nevada Independent: 0.3%Fundamental Attribution Error2.1%This article: 4.2%Piper Heath: 0.4%The Nevada Independent: 0.1%Actor-Observer Bias4.2%This article: 0.0%Piper Heath: 1.5%The Nevada Independent: 1.0%In-Group Bias0.0%This article: 0.0%Piper Heath: 0.3%The Nevada Independent: 0.3%Out-Group Homogeneity Bias0.0%This article: 0.0%Piper Heath: 0.7%The Nevada Independent: 0.6%Halo Effect0.0%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.1%Horn Effect0.0%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.0%Dunning-Kruger Effect0.0%This article: 2.8%Piper Heath: 0.5%The Nevada Independent: 0.8%Recency Bias2.8%This article: 0.0%Piper Heath: 0.1%The Nevada Independent: 0.1%Primacy Effect0.0%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.0%Blind-Spot Bias0.0%This article: 0.0%Piper Heath: 0.3%The Nevada Independent: 1.6%Ad Hominem0.0%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.5%Straw Man0.0%This article: 2.7%Piper Heath: 2.4%The Nevada Independent: 1.5%Appeal to Authority2.7%This article: 0.0%Piper Heath: 0.8%The Nevada Independent: 1.0%False Dilemma0.0%This article: 2.4%Piper Heath: 1.0%The Nevada Independent: 0.5%Slippery Slope2.4%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.1%Circular Reasoning0.0%This article: 3.6%Piper Heath: 0.9%The Nevada Independent: 2.6%Hasty Generalization3.6%This article: 4.7%Piper Heath: 0.6%The Nevada Independent: 0.2%Red Herring4.7%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.3%Bandwagon0.0%This article: 8.0%Piper Heath: 4.0%The Nevada Independent: 2.3%Appeal to Emotion8.0%This article: 0.0%Piper Heath: 0.2%The Nevada Independent: 0.4%Begging the Question0.0%This article: 0.0%Piper Heath: 0.3%The Nevada Independent: 1.2%Post Hoc (False Cause)0.0%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.0%Tu Quoque0.0%This article: 1.3%Piper Heath: 0.4%The Nevada Independent: 0.4%Burden of Proof1.3%This article: 0.0%Piper Heath: 0.4%The Nevada Independent: 0.1%Appeal to Nature0.0%This article: 0.0%Piper Heath: 0.2%The Nevada Independent: 0.3%Composition/Division0.0%This article: 4.8%Piper Heath: 0.6%The Nevada Independent: 1.0%Anecdotal4.8%This article: 0.8%Piper Heath: 0.1%The Nevada Independent: 0.1%No True Scotsman0.8%This article: 10.3%Piper Heath: 1.3%The Nevada Independent: 0.6%Ambiguity (Equivocation)10.3%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.0%Gambler’s Fallacy0.0%This article: 2.4%Piper Heath: 0.2%The Nevada Independent: 0.1%Middle Ground2.4%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.1%Personal Incredulity0.0%This article: 0.0%Piper Heath: 0.4%The Nevada Independent: 0.3%Special Pleading0.0%This article: 5.1%Piper Heath: 0.4%The Nevada Independent: 0.1%Genetic Fallacy5.1%This article: 2.1%Piper Heath: 0.6%The Nevada Independent: 0.7%Unattributed Quote2.1%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.5%Quote-first Misdirection0.0%This article: 1.9%Piper Heath: 0.4%The Nevada Independent: 2.7%Biased Writer Voice1.9%This article: 0.0%Piper Heath: 1.0%The Nevada Independent: 1.0%Indoctrination0.0%This article: 0.0%Piper Heath: 0.0%The Nevada Independent: 0.4%Politically Left Leaning Bias0.0%This article: 0.0%Piper Heath: 0.2%The Nevada Independent: 0.7%Politically Right Leaning Bias0.0%This article: 0.0%Piper Heath: 0.1%The Nevada Independent: 0.3%Attempt to Sell a Product or S…0.0%

1300 words analyzed.

Speakers

10speakers42%attributed speech751writer words
Selected voice

Hockaday

100%flagged-word coverage
127 attributed words23% of attributed speech52% writer coverage
0%5.0%10.0%Biased Writer Voice+6.8 ptsWriter: 1.9%Hockaday: 8.7%8.7%Unattributed Quote-3.6 ptsWriter: 3.6%Hockaday: 0.0%0.0%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.