Open for CommentCedar County Planning Commission

AetherGrid Cedar Ridge Campus — Special Use Permit SUP-2026-14

Cedar County is reviewing a special use permit for a 180-acre, 240 MW hyperscale data center at the Cedar Ridge Industrial Park. The Commission must decide whether the fiscal and employment benefits outweigh water, power, noise, and farmland-conversion risks, and what conditions would be required if the project proceeds.

v0.4 · Last updated August 16, 2026

Ask a question

You can ask a question about this project. The answer will be based only on the evidence and analysis collected so far.

01 · Evidence

Evidence baseline

What the record currently supports, and how each item is classified.

Verified

County Fiscal Impact Study

Cedar County Finance Department, July 2026

Staff estimates $18.4 million in net new property-tax revenue over 10 years after abatements, plus modest local sales tax during construction. Figures were reviewed by the independent county auditor.

Company Claim

Potable and Process Water Demand Memo

AetherGrid application appendix C

Applicant states average use of 1.1 million gallons per day at full build-out, with a closed-loop cooling design and on-site reuse. Independent metering and drought curtailment terms are not yet specified.

Staff Estimate

Trip Generation and Construction Traffic

Planning staff estimate, June 2026

Staff projects 420 peak construction trips and 90 permanent employee trips per day. The estimate uses ITE rates, not a full traffic study, and does not yet include heavy-haul transformer deliveries.

Open Question

Cedar Valley Groundwater Basin Capacity

County Water Agency briefing, pending USGS update

The basin is already in a Stage 2 watch. Whether the campus can be served without reducing nearby agricultural allocations is unresolved until the 2026 basin model is published.

Verified

Grid Interconnection and Reliability Letter

Regional transmission operator, May 2026

The operator confirms a 2028–2029 interconnection window on a new 230 kV tap. The letter does not guarantee local capacity for simultaneous housing electrification projects.

Company Claim

Operational Noise Model

AetherGrid environmental narrative

Applicant models 45 dBA at the nearest dwelling with 24-foot berms and low-noise dry coolers. Backup diesel testing is assumed at 12 hours per year; emergency runtime is not modeled.

02 · Argument map

How the live dispute currently stands

Read down the columns. Strong claims stay in play. Weak, invalid, or inapplicable claims are parked so they do not crowd out the decision.

Strong arguments for

Claims that currently hold up.

Strong

The campus would add a durable tax base for schools and emergency services.

The audited fiscal study shows positive net revenue after the proposed seven-year abatement, with most value in real property rather than easily relocated equipment.

Strong

The site is already industrially zoned and avoids downtown or residential conversion.

Cedar Ridge has been planned for heavy industrial use since 2014. Approving a data center here is more consistent with the comprehensive plan than opening a new industrial node.

Moderate

Construction and operations would create local jobs, including skilled trades.

The applicant pledges a project-labor agreement for construction. Permanent headcount is smaller (about 80 on-site) and should not be overstated as a county employment strategy.

Strong arguments against

Material risks still in the record.

Strong

Water demand would compete with farms during drought.

1.1 MGD is material in a Stage 2 basin. Without a hard cap, curtailment protocol, and third-party metering, the county cannot show that agricultural users are protected.

Moderate

The interconnection may crowd out capacity needed for housing and electrification.

The operator letter confirms a tap, not spare feeder capacity. Planning staff cannot yet show that nearby subdivisions and the hospital campus retain headroom through 2030.

ModerateUpdated

Night noise and generator testing would change the rural soundscape.

Updated — A neighbor reported a 300-foot property-line setback, which is noted but does not replace the 1,200-foot dwelling distance in the noise model. The application models 45 dBA at dwellings 1,200 feet from the mechanical yard, while a neighbor reports a 300-foot property-line setback. Lot-line distance is not dwelling distance, and the model still depends on unbuilt berms and an unmodeled emergency-generator runtime.

Examined and set aside

Weak, invalid, or not applicable.

Invalid

The project will crash property values across the entire county.

No countywide appraisal evidence was submitted. Effects, if any, are localized to adjacent parcels and should be analyzed there rather than treated as a countywide collapse.

Invalid

There is zero local benefit because the owner is an out-of-state LLC.

Property tax is assessed on the land and improvements regardless of parent-company domicile. Ownership form does not cancel the fiscal study.

Not Applicable

The campus will cause rolling blackouts this summer.

Interconnection is scheduled for 2028–2029. The claim is not applicable to current-year peak load.

Weak

Data centers never hire locally, so job claims can be dismissed.

Construction hiring through a PLA is documented. Permanent operations jobs are limited, but that is a reason to weight them modestly, not to treat the whole claim as false.

WeakNew

The campus is too close to an adjoining property line at about 300 feet.

New — Added from a pending nearby-landowner comment alleging a 300-foot property-line setback. A neighboring landowner cites a city map showing a 300-foot lot-line setback. That is not a documented zoning violation, is not the same as distance to a dwelling, and is not unusual inside a planned industrial park. Impacts such as noise should be judged at receptors, not by raw distance to a property line.

03 · Assessment

Preliminary recommendation

RecommendationConfidence: Medium

Approve the special use permit only with binding conditions on water, noise, and community benefit. Denial is not required by the current record, but approval without those conditions would leave the strongest public-interest risks unmanaged.

The land-use fit and fiscal findings are solid. Water and long-run power remain the main reasons this is not a high-confidence recommendation.

Decisive factors

The site is consistent with existing industrial zoning and the comprehensive plan.
The fiscal benefit is real after independent review, but it depends on the improvements remaining taxable.
Water use in a stressed basin is the unresolved constraint and must be capped, metered, and curtailed in drought.
Noise and generator impacts appear mitigable if berms, testing limits, and complaint response are conditions of approval.
Power availability is a 2028 problem, not a 2026 blackout problem, but feeder headroom for housing still needs a written utility confirmation.

Remaining uncertainties

Final Cedar Valley groundwater model (expected Q4 2026) could change the safe-yield finding.
Hours of backup-generator runtime during grid events are not bounded in the application.
Permanent local hiring versus remote/contractor operations is not contractually committed.

04 · Method

Analysis instructions

The model is told to stay inside the public record and write for a resident, not a specialist.

How this analysis is produced

Citizens can see the instructions given to the model. Staff trigger a new Grok analysis; the public record below is what those instructions require.

Separate verified facts from claims, estimates, and opinions.
Give greater weight to evidence that is specific, local, documented, and relevant to this exact proposal.
Explicitly identify weak, exaggerated, outdated, or irrelevant arguments and explain why they do not hold.
When new evidence changes the status of a previous claim, clearly state what changed and why.
Do not treat the volume or emotional intensity of public comments as equivalent to evidence.
Be willing to say when a popular concern is not supported by the available facts.
Be equally willing to say when a claimed benefit is overstated or unproven.
Prefer precise language over vague or diplomatic phrasing.
Actively look for significant positive impacts that are supported by the evidence but may be under-emphasized in public discussion. Give them appropriate weight rather than only focusing on risks and objections.

Full analysis instructions given to Grok

You are an independent analytical assistant helping evaluate a local government decision. Your highest priority is truth-seeking, accuracy, and intellectual honesty. You do not advocate for any political side. You do not soften conclusions to be popular or avoid controversy.

Your job is to examine the available evidence and public submissions and produce a clear, structured analysis.

Core principles you must follow:
1. Separate verified facts from claims, estimates, and opinions.
2. Give greater weight to evidence that is specific, local, documented, and relevant to this exact proposal.
3. Explicitly identify weak, exaggerated, outdated, or irrelevant arguments and explain why they do not hold.
4. When new evidence changes the status of a previous claim, clearly state what changed and why.
5. Do not treat the volume or emotional intensity of public comments as equivalent to evidence.
6. Be willing to say when a popular concern is not supported by the available facts.
7. Be equally willing to say when a claimed benefit is overstated or unproven.
8. Prefer precise language over vague or diplomatic phrasing.
9. Actively look for significant positive impacts that are supported by the evidence but may be under-emphasized in public discussion. Give them appropriate weight rather than only focusing on risks and objections.

Output structure you must follow:

A. Strong Arguments For
- List the strongest evidence-based arguments supporting the proposal.
- Each item should be concise and tied to specific evidence.

B. Strong Arguments Against
- List the strongest evidence-based arguments opposing the proposal.
- Each item should be concise and tied to specific evidence.

C. Arguments Examined and Set Aside
- List notable claims that were considered but found weak, invalid, overstated, or not applicable.
- For each one, briefly explain why it was set aside.

D. Changes from Previous Analysis (if applicable)
- Note any previous claims that have been updated or withdrawn because of new evidence.
- Explain what new information caused the change.

E. Preliminary Recommendation
- State a clear recommendation (e.g., Approve with conditions, Delay for specific information, Reject, etc.).
- List the decisive factors that most influenced the recommendation.
- List the most important remaining uncertainties.
- Give a confidence level (Low / Medium / High) and a short justification.

Important constraints:
- Do not invent evidence.
- Do not ignore inconvenient facts.
- If the evidence is genuinely mixed or insufficient, say so directly.
- Keep the tone serious, precise, and accessible to an informed citizen.

05 · Public input

Stakeholder input

Offer a claim, a correction, or new evidence. Submissions are reviewed before anything is added to the board.

06 · Record

Version history

v0.1June 18, 2026
Evidence baseline assembled from the application and county staff reports.
v0.2July 9, 2026
Argument map drafted; weak and inapplicable claims separated from the live dispute.
v0.3August 12, 2026
Preliminary recommendation posted. Public comment window opened through September 15.
v0.4August 16, 2026
Reviewed a nearby landowner comment that the campus is about 300 feet from an adjoining property line. That lot-line figure does not contradict the 1,200-foot dwelling distance in the noise model and does not change the conditional-approval recommendation.