One Meeting Is Not One Story
Charlotte's council met for six hours on a Monday night. We got seven stories out of it, and found out that only one of the night's vote counts could be confirmed anywhere else.
At the end of August, my AI offered to build me something we already had. It was one of six times that day it told me something didn't exist. The fix wasn't a smarter AI.
Read the noteCharlotte's council met for six hours on a Monday night. We got seven stories out of it, and found out that only one of the night's vote counts could be confirmed anywhere else.
I asked for a new look for the tool I run sixteen publications from. I got two, hated both, and it turned out the colors were never the problem.
Patch's AI newsletter reaches nearly a million subscribers, and no person touches it before it sends. We pointed our AI at the town's own records instead, starting with an arrest log nobody else keeps.
In April I said Mercury Local was a platform. Six months on: sixteen publications, a paper launched in a day, and local businesses who wanted it too.
Peter Cellino spent a year building AI-assisted editorial infrastructure. Today he wrote about a police blotter. It's not ironic — it's the point.
Most conversations about AI governance treat it as a configuration problem. That is setup. At Mercury Local, governance is the document written after each failure — eleven rules, each one traceable to a specific mistake the system made and will not make the same way again.
Richard Tofel and Dan Kennedy make the best available argument for reader-revenue journalism — and they're right. The logic holds. But the conclusion that follows — that paywalls are therefore a tool of independence — is where I'd push back.
Opens on Mercury Local