AI + AI security collective · Northeast Florida
Prompt in. Payload out.
~/about
Three of us kept having the same conversation in group chats and hallways, so we gave it a room and a schedule, right here in St. Augustine. Everyone here works on this stuff for real, whether that means shipping agents, breaking them, defending them, or all three in the same week.
There's no keynote, no sponsor slot, and nobody is trying to sell you a platform. If you show up, you're expected to have opinions and be willing to change them. If you're anywhere in Northeast Florida and this sounds like your kind of room, it probably is.
~/tracks
One is small and steady. One is open and louder. They feed each other.
A working group, not an audience. We take turns bringing something we're stuck on or excited about and the rest of the room digs in. Half the value is the argument afterward.
The door is open. Come for a talk or a demo, stay for the part where you meet people who do what you do. New to AI security is fine. Curious and from a totally different discipline is also fine.
~/topics
Roughly this, though it moves as fast as the field does. Nobody has to be an expert in all of it, and most of us aren't.
Direct and indirect. What actually works, what defenses hold up, and which ones only look like they do.
What happens when a model gets hands. Permission design, loop control, and the blast radius of one bad call.
What servers expose, how tools get abused, and what a sane gateway between a model and your systems looks like.
Retrieval pipelines, tenant separation, and all the ways context ends up somewhere it shouldn't.
Model provenance, weights you didn't build, and the dependency tree hiding underneath a two line install.
What to capture from a non-deterministic system, and how to tell a real incident from a model having a bad day.
Testing things that answer differently every run. Building harnesses that catch regressions instead of vibes.
Half of this is construction, not critique. People bring working code and get told what's wrong with it.
~/core
It stays small because that's the whole point. Ten people can argue productively. Forty people watch two people argue.
Some of this turns into work. People pair up on projects, and start-up ideas get taken seriously here, up to and including the funding conversation when one earns it. That's encouraged but never required. Plenty of members just come to think out loud with people who get it.
~/nights
Here's the shape we're planning, give or take. We keep the talking short and the talking-to-people long.
Doors and hanging out.Show up late, it's fine. Nothing starts on the dot.
Twenty minutes on something someone actually did.Working code and real findings beat slideware.
Shorter. Sometimes a demo, sometimes a live teardown.The ones that fail on stage are usually the best ones.
Open floor. This is the part most people come for.Questions, arguments, and swapping notes.
The first one lands in October or November 2026 in St. Augustine, venue in the works. Follow the calendar and you'll get the date the moment it exists.
~/next
Things we want to build into the group as it finds its feet. None of this is live yet, and we'd rather ship it right than announce it early. If you'd want in on any of it, that's worth mentioning when you reach out.
Pairing people newer to the field with people who've been at it a while. Both sides of that are welcome here.
Small collaborative projects that end in something published, not a doc that dies in somebody's drive.
What we're reading, breaking, and building, on a schedule we can actually keep. Signal, no filler.
~/join
Pick the door that fits. Neither one costs anything.
Open to anyone, and the first one is coming in October or November. Follow the calendar and you're on the list for the date. You don't need to work in security and you don't need to know anyone.
Follow the calendarSmall and invite based, but we're not precious about it. Tell us what you're working on and why this sounds like your kind of room. Coming to a public night first is the easiest way in.
Start a conversationOr reach us directly at EDIT: email address.