The Tax Break Vote Nobody Saw Coming

So, here's a question that's been rattling around in my head for a while now.

If a government body holds a meeting, and they vote on something big, and technically it happened—but the way it happened is the whole argument—did it actually happen the way it was supposed to?

I'm not a lawyer.

I'm barely coherent on parliamentary procedure.

But I keep bumping into this same pattern with the Faircrest Data Center project in Perry Township, and I finally found a piece of it that actually makes sense to write about.

Digging Into an Executive Session

Back in March—March 24th, 2026, to be exact—Perry Township Trustees approved a tax break for Faircrest.

That's the headline.

The resolution passed.

Tax incentive: approved.

Here's the part that stopped me cold.

According to the Canton Repository article I found (via AOL, since apparently that's how I source news now), the Trustees approved this tax break after an executive session.

An executive session.

Which is a closed meeting.

Behind closed doors.

And here's where I started wondering: what exactly happens in those closed meetings, and who gets to know about it?

The Open Meetings Act Problem

Look, I didn't invent the Open Meetings Act.

Ohio did.

It's a law that says public bodies have to conduct public business in public, with some narrow exceptions—personnel, legal advice, real estate negotiations, that kind of thing.

The exceptions exist for reasons.

Sometimes you actually do need to talk privately about sensitive stuff.

But here's the thing that makes me uncomfortable.

An executive session on a tax incentive?

That's when I started asking whether someone already had a problem with how this was supposed to work.

And I found out: yeah.

Someone did.

Stark Civic Monitor independently verified that there's an Open Meetings Act allegation connected to this vote.

Not verified by me personally—I just organize documents and ask AI to help me see patterns in them—but verified by the site's own tracking against the source material.

The allegation exists.

It's real.

It's tied to this specific tax vote in Perry Township.

That's different from knowing whether the allegation is true.

That's just knowing whether it got filed.

What Does This Actually Tell Us?

Here's the thing about being a tech nerd who accidentally wandered into local government.

I can find documents.

I'm getting better at organizing them.

I can see when two things are connected because they both mention the same project, the same date, the same people or places.

But I genuinely don't know what an Open Meetings Act violation actually means in practice.

I don't know the legal standards.

I don't know what happens next if someone files an allegation.

I don't know whether this one will go anywhere.

What I do know is this: tax incentives for major development projects are kind of important to how the entire local economy gets shaped over the next decade.

And the process for voting on them is supposed to follow rules.

Rules that exist partly so regular people can actually understand what happened and why.

If the process itself becomes the argument, then I think that matters.

Even if I'm not equipped to referee what it means.

Why I'm Tracking This

Here's my honest ethical problem with this stuff.

I'm building a tool to help people see government records and public filings side by side.

That's neutral work.

But "neutral" doesn't mean "useless."

It means I'm not deciding whether Faircrest should get the tax break or whether the Trustees made the right call.

It means I'm making it possible for someone else to see what was filed, what was alleged, what the official record says, and what people are saying about the same event—all at once, without spending three hours hunting through a county website.

If that information helps someone make a better decision—whether they're a resident, a developer, an official, or a lawyer—then the work matters.

Even if I'm just the guy organizing the puzzle pieces instead of solving the puzzle.

That's What the Dossier's For

This is exactly why I built the project dossier feature on Stark Civic Monitor.

One development project.

Multiple pieces of public record tied to it.

Tax votes, meeting agendas, allegations, articles, permits—all tracked, all verified, all sitting together so you can see the whole shape of what happened instead of chasing one document at a time.

Faircrest's got a full dossier now.

The tax break vote is in there.

So is the Open Meetings Act allegation.

And as more stuff gets filed or reported, it all stays connected.

That's the whole point.

Not because I'm auditing anybody.

Just because when this much is happening in one county, in one township, around one project, it's hard to see the full picture if you're only looking at one piece at a time.