Eighty minutes into building with three people I had met that morning, I renamed the idea I brought with me.
I wrote that commit message myself.
By then the idea had four authors.
Some context on the room.
The Claude Impact Lab is part of Claude Community, the run of local events where people who use Claude get together in person.
This one followed a Claude Conversation held earlier in Los Angeles, where people talked through what AI is doing to their jobs.
The Impact Lab takes what came out of that conversation and turns it into a build day.
You get the problem brief, you form a team, you have the day, you demo at the end.
Travis Johnson, a Claude community ambassador, hosted with Evan Grenda at Intersections LA.
Developers and non-developers both, and they meant it.
What I brought was not a project.
It was an idea and a spec for it.
No code, nothing built, nothing running.
The idea comes out of something that is true in most cities.
Your city government publishes what it intends to do before it does it.
Agendas go up ahead of the meeting, and any resident can read them, show up, and speak on an item before the vote.
That right exists.
Using it takes work, which is probably why every time I used it I would give up on what I was looking for.
In Ventura it means 21 separate boards and commissions, each with its own page, posting PDFs that run long and read like they were written for the people already familiar with the subject matter.
Because they were.
So if you want to know whether anyone is voting on something a block from your house, you go looking, board by board, document by document.
And you have to already know the words the city uses for the thing you would call a pothole.
Agenda Watch was going to make all of that searchable in plain language, with every answer carrying a receipt back to the page it came from, so nobody has to take the tool's word for anything.
In use that is a small thing.
You ask a question about an item on a city agenda the way you would say it out loud.
Is there anything about short term rentals?
You get back the agenda items that match, each one carrying the group that met, the meeting date, the item number, the page range, and a link to the source PDF.
You read the plain-language version, then you click through and check the original yourself.
Search, and receipts.
That is the whole solution to an opaque search.
I wrote the spec for a Google hackathon and then found out I could not enter, because I am a government employee.
So it sat.
A plan with nowhere to go.
The first commit in that repo is from the build session at the Claude Lab.
The core of CiviQ was written that day, by four people who had just met.
When I got there, I was not worried about building a project.
I have been building for a while now and I know what I can do with Claude Code.
I was worried about the other part.
I build alone because I am shy, and alone is where I am comfortable.
Idea, plan, implement, present, all of it me.
I had done a group build once, about a year ago.
Since then, solo.
And under that, the worry I'm trying to get better at voicing so it becomes less of a worry.
What are engineers going to think of an AI-assisted builder?
Am I going to be taken seriously in a room with people who can write the lines themselves?
Somebody filed an issue on my repo and I did not know if that was normal Partway into the build, Jesus Gutierrez started filing GitHub issues against the repo.
Corrections, changes, improvements.
One after another while I was in the editor.
I had never had that happen before in my builds.
Not once.
My repos are places I go alone, and the issues tab is a thing other people's projects have.
I remember thinking, is this a normal thing that builders do all the time to contribute to each other's projects?
Is this how it works?
It is normal.
It is how teams track work without tapping each other on the shoulder every four minutes.
I had to look it up afterward to be sure, which tells you exactly how much co