A practical guide for residents who want to verify claims from any source — including this one.
This site is a community information aggregator. It collects, organizes, and summarizes information from local and regional news outlets, official government documents, public records, and published research. It is not an original investigative news outlet. It does not have reporters at every council meeting, lawyers reviewing every document, or scientists conducting independent environmental tests.
That distinction matters. When this site says "the Toledo Blade reported" or "Acting Law Director Fifer issued an opinion," those are references to primary or secondary sources you can check yourself. When this site makes an analytical judgment — for example, characterizing the AG's response as declining to endorse the law director's ruling — that is an interpretation of a public document, and you should read the document yourself and form your own view.
The core principle:
No single source — not this site, not the city, not the developer, not any news outlet — should be your only source on a decision this significant. The goal of this page is to give you the tools to check everything, including what you read here.
Information literacy researchers at the Stanford History Education Group and the University of Washington have developed practical frameworks for evaluating online information. One widely taught approach is SIFT:
Before reading, sharing, or reacting to a claim, pause. Ask: do I already have a strong opinion about this? Strong prior opinions make us more likely to accept confirming information uncritically and reject contradicting information reflexively.
Before reading the content, find out who produced it. Is this a news outlet with editorial standards? A government agency? A developer's PR document? A community advocacy group? Each has different incentives and different obligations to accuracy.
If a claim matters, search for it independently. Skilled fact-checkers open multiple tabs and check what other credible sources say about the same claim before deciding what to believe. If only one source is making a claim, that is a signal to be cautious.
Follow claims back to their original source. A claim that "studies show data centers create 100 jobs" should be traceable to a specific study you can read. If you can't find the original, treat the claim as unverified.
Source: SIFT framework developed by Mike Caulfield, University of Washington. See also: Stanford History Education Group's Civic Online Reasoning curriculum.
Professional fact-checkers use a technique called lateral reading: instead of reading deeply into a single source to evaluate it, they immediately open new tabs and search for what others say about that source. This is more effective than trying to evaluate a source from the inside.
Applied to the Oregon data center story, this means:
When you see a claim from Capacity Infrastructure LLC
Search for "Capacity Infrastructure LLC" and "Upterra Group" in a new tab. What do independent journalists, regulators, or community groups say about this company? Are there other communities where they have developed projects? What were the outcomes?
When you see a claim from the city of Oregon
Check whether the claim appears in official meeting minutes, ordinances, or public statements — not just press releases or social media. Official documents are harder to revise after the fact and carry legal weight.
When you see a claim from this site
Check the source cited. If a claim cites the Toledo Blade, find the article. If it cites a council meeting, watch the recording. If it cites a legal document, read the document. This site links to primary sources wherever possible — use those links.
When you see a claim on social media
Social platforms are optimized for engagement, not accuracy. Before sharing, search the claim in a news search engine. If credible outlets haven't reported it, that is meaningful. If they have, check whether the social post accurately represents what they reported.
These are the original documents and official sources for the Oregon data center story. When evaluating any claim about this project, these are the places to go first.
Meeting agendas, minutes, and ordinance text. The authoritative record of what council voted on and what the exact language of each ordinance was.
Recordings of city council meetings. If you want to know exactly what a council member said, watch the meeting. Written summaries — including those on this site — are interpretations.
Official city statements, the city's own FAQ on the data center project, and contact information for elected officials.
Recordings of Ohio General Assembly committee hearings and floor sessions. If a bill is being debated, you can watch the testimony.
Full text of every bill mentioned in this story — HB 646, HB 695, HB 706, HB 710, and the Senate Democrats' package. Read the actual bill language, not just summaries.
The 31-page draft general permit for data center wastewater discharges. Read the actual document — not just characterizations of it — before forming an opinion.
The regulatory body overseeing electric rate cases in Ohio. Proceedings related to data center rate impacts are filed here and are public record.
Capacity Infrastructure Q&A Letter (February 27, 2026)
The developer's own written answers to community questions. Available through the city of Oregon's public records. This is the primary source for the developer's stated positions on water, cooling, jobs, and community benefits.
Acting Law Director Fifer's Legal Memorandum (February 2026)
The six-page legal opinion concluding that the 3-2 vote was valid. Available through the city of Oregon's public records. Read the actual reasoning — not just the conclusion — before forming a view on the vote's legality.
These outlets have published original reporting on the Oregon data center story. They have editorial standards, named reporters, and correction policies — which means errors can be identified and addressed. This does not mean every article is perfect, but it does mean there is accountability.
| Outlet | Coverage Focus | Notes |
|---|---|---|
| Toledo Blade | Local politics, council votes, state legislation | Primary regional daily; most comprehensive ongoing coverage |
| Ohio Capital Journal | State legislation, statewide data center policy, moratoriums | Nonprofit investigative outlet; strong on statehouse coverage; free to read |
| WTOL 11 | Council meetings, community response, moratoriums | Local TV news; strong on meeting coverage and community reaction |
| 13ABC | Community impact, regional data center developments | Local TV news; covers Northwest Ohio broadly |
| Press Publications | Oregon-specific council coverage, local community detail | Local community paper; most granular coverage of Oregon city government |
| Toledo Free Press | Regional economic development, RGP coverage | Regional business and civic coverage |
| Signal Ohio / Columbus Dispatch | State politics, veto override, legislative developments | Statewide coverage; strong on Columbus-based political developments |
This list is not exhaustive. Other credible outlets — including NBC4i, Cleveland.com, and Axios Columbus — have also covered aspects of this story. When a claim appears in multiple independent outlets, that is a stronger signal of accuracy than when it appears in only one.
These are patterns that should prompt skepticism, regardless of whether the claim comes from a source you agree with or disagree with.
No source cited, or the source is the same organization making the claim
A developer citing its own marketing materials, or a city citing its own press release, is not independent verification. Look for third-party confirmation.
Round numbers without methodology
"$26 in tax revenue for every $1 in services" is a real figure — but it comes from Loudoun County, Virginia, the world's largest data center market, under conditions that may not apply to Oregon. Ask: where does this number come from, and does the methodology apply here?
Conditional commitments presented as done deals
"Expressed strong interest" is not the same as a signed agreement. "Moving toward finalization" is not the same as finalized. Read the exact language of any commitment before treating it as binding.
Characterizations of legal documents without quoting the actual language
The AG's response has been characterized in multiple ways by multiple parties. The actual text is short and unambiguous. When a legal document is being discussed, find the document and read it.
Urgency framing that discourages deliberation
Claims that a decision must be made immediately, that there is no time for questions, or that asking for more information is obstructionist should prompt more scrutiny, not less. Legitimate decisions can withstand deliberation.
Claims that only appear on social media or anonymous sites
If a significant claim about this project has not been reported by any of the outlets listed above, that is a reason to be cautious. It does not mean the claim is false — it means it has not been independently verified.
Alongside the red flags, there are positive signals that a claim is well-grounded:
Named sources with verifiable roles
A quote attributed to "Acting Law Director Chynna Fifer" is more verifiable than a quote attributed to "a city official." Named sources can be contacted, and their statements can be checked against the public record.
Links or citations to primary documents
When a claim links directly to the ordinance text, the meeting recording, or the regulatory filing, you can check the source yourself. This is a sign of confidence in the underlying evidence.
Acknowledgment of uncertainty
Sources that say "this has not been independently verified" or "the outcome remains pending" are being honest about the limits of their knowledge. Overconfident sources that present everything as settled should be treated with more skepticism.
Corroboration across independent sources
When the Toledo Blade, WTOL, and the Ohio Capital Journal all report the same fact independently, that is strong evidence the fact is accurate. Single-source claims deserve more scrutiny.
This site was built with the assistance of AI tools. That is worth being transparent about, because AI-assisted research and writing carries specific risks that readers should understand.
Large language models can generate credible-sounding but false political or policy content. They can misattribute quotes, confuse dates, and present plausible-but-wrong characterizations of legal documents. The training data underlying these models is scraped from the open internet, which includes misinformation, coordinated political manipulation, and "data voids" where fringe narratives dominate.
The way this site attempts to mitigate those risks is by grounding every factual claim in a named, linkable source — a specific news article, a specific public document, a specific official statement. Where a claim is characterized as disputed or unverified, that characterization is intentional. Where a source is cited, you can check it.
What this means for you as a reader:
Do not treat this site as a substitute for primary sources. Use it as a starting point — a map of the terrain — and then go to the original documents, the meeting recordings, and the news articles to form your own informed view. The links and citations on this site exist precisely so you can do that.