Doug Conrad, founder of Stark Civic Monitor

What the Developer Says About Power

So there's this thing I keep running into while building out the Stark Civic Monitor database.

Developers file documents.

Governments file documents.

News outlets report on documents.

And sometimes all three are talking about the same project, and sometimes they're not quite talking about the same thing, even though the words sound identical.

A contractor wants to know: where's the power coming from for this thing?

A resident wants to know: will the grid handle it?

A regulator wants to know: what's the infrastructure impact?

And a developer wants to know: how do I explain where the power's coming from?

Those aren't quite the same question.

Tracking What the Developer Says

I was cataloging data for Project Shelby recently—one of the larger developments being tracked on the site—and I came across a detail that stopped me for a second.

The developer, Panattoni, made a claim about utilities back in August.

Specifically, they said AEP Ohio would be handling the power.

That's it.

That's the whole claim.

No details about capacity, no timeline, no agreement documentation, nothing beyond: AEP Ohio.

Here's the thing though: I logged it in the project dossier with a specific flag.

"This is what the DEVELOPER said—not independently verified."

And I want to be really plain about why that flag matters.

Why That Distinction Exists

A lot of what gets said about a project is true.

Some of it probably isn't.

Most of it is somewhere in between—technically accurate but missing context, or accurate under certain conditions that might or might not hold up later.

When Panattoni says "AEP Ohio handles the power," that's a statement of fact that can presumably be verified or contradicted by AEP Ohio themselves, by regulatory filings, by interconnection agreements, by literally anybody with access to the paperwork.

But the moment I log it as if it's confirmed fact rather than the developer's claim, I've already made a choice about what to believe.

I've also made it harder for someone reading the site later to know where that information originally came from.

I don't know AEP Ohio's capacity situation.

I don't know if they've already committed to this project.

I don't know if there's some regulatory process that still needs to happen.

I know what Panattoni said to a news outlet.

That's actually useful information.

But it's a different kind of useful than "AEP Ohio is confirmed as the utility provider."

The Bigger Problem

The reason I'm even thinking about this is because I watch how information moves around.

A developer makes a statement.

A news outlet reports the statement.

Someone reads the news article and shares it as fact.

Someone else reads the share and cites it as evidence.

By the time the claim reaches the fifth person, nobody remembers it started as what one company said in August.

It just sounds like how things are.

And maybe they are.

But maybe they're not.

Maybe the utility situation changed.

Maybe there's a permitting step that hasn't happened yet.

Maybe AEP Ohio said yes to one thing but not another.

I genuinely don't know.

That's not because I haven't looked hard enough—it's because that information might not be public yet, or it might be in a filing I haven't found, or it might not exist until someone signs something.

That's Where the Site's Job Gets Tricky

Here's my honest problem with what I'm building.

I want Stark Civic Monitor to be trustworthy.

That means I need to be really careful about the difference between "this is documented fact" and "this is what someone claimed."

But I also need the site to be useful.

And if I flag everything as unverified until I can personally confirm it through seventeen different official sources, the site becomes useless, because I'm one person with a day job, not a government records department.

So I'm making a choice.

I'm going to log what people say, and I'm going to mark it with what I actually know about where it came from.

Developer claims, news reports, permit applications, official filings—they all get tracked, they all get labeled with their source, and the person using the site can decide what weight to give each one.

That's not the same as investigative journalism.

It's not even close.

It's more like: here's what got said, here's who said it, here's where I found it, now you go read it yourself and make up your own mind.

Why That Matters Right Now

Stark County's got a lot happening.

Multiple projects, multiple utilities, multiple companies all making statements about infrastructure, timelines, and capacity.

Some of those statements will turn out to be completely accurate.

Some will turn out to be incomplete.

Some might change before anything gets built.

If you're a contractor trying to figure out if a job's real, or a property owner trying to understand what's coming, or just someone who lives here trying to know what's actually planned—you need to see what got said, when it got said, and who said it.

The Stark Civic Monitor dashboard lets you do that.

You can see the developer's claim about utilities right alongside the permit filings, the news coverage, the public meeting minutes, and whatever else got tracked on that project.

That side-by-side view is the whole point.

It's not my job to tell you what to believe.

It's my job to make sure you can see what actually got said, and where it came from.

Then you decide what you think.

Today's topic: the Project Shelby Project Dossier · Permalink

Comments

No comments yet - be the first.

Comments are reviewed before they appear - this is a locally sensitive topic and I'd rather moderate a little slower than let it turn into a free-for-all. Yours will show up here once approved.

← Back to Stark Civic Monitor · All Posts