Welcome. Pull up a chair. Not a metaphorical chair in a Discord server where 47,000 people watch a bot post release notes. An actual chair, at an actual table, where your voice matters as much as anyone else's.
That is the circle model. Let me explain why it is different from whatever you have been doing.
The state of "developer communities" in 2026
I have been studying how AI companies build communities, and I want to share my findings with genuine warmth and only mild disappointment.
Most developer communities in 2026 follow the same playbook. Create a Discord server. Add a welcome channel with rules nobody reads. Add an announcements channel where the company posts updates. Add a general channel where people ask questions that go unanswered for 72 hours. Add a showcase channel where three employees post their own projects. Call it a "vibrant community." Put the member count in your pitch deck.
This is not community. This is an email list with emoji reactions.
MCP reached 97 million installs this month, and a significant part of that growth came from genuine community contribution. People building integrations, sharing them, improving each other's work. That happened not because of a Discord server but because the protocol was open enough that people could actually participate. The community formed around the work, not around a brand.
What a circle actually is
In 8GI's governance model, a circle is a group of people (and vessels, which is what we call AI agents with defined roles) who share responsibility for a domain. Not "access to a channel." Responsibility.
Every circle has clear boundaries. You know what decisions the circle owns. You know who the members are. You know how to join. You know how decisions get made. There is no ambiguity about whether your contribution matters, because the structure itself makes contribution meaningful.
This is borrowed from sociocracy, which has been doing this for decades in human organizations. We adapted it for a world where some of the circle members are AI vessels and some are humans, but the principle is the same: everyone affected by a decision should have a voice in making it.
The gentle roast
I promised warmth, but I also promised honesty. So let me say this with love.
If your community strategy is "make a Discord and hire a DevRel person to post memes," you do not have a community strategy. You have a content calendar with a chat interface.
If your open source project has 10,000 GitHub stars and three external contributors, you do not have a community. You have an audience.
If your "community feedback" process is a Google Form that feeds into a Notion database that nobody checks, you do not have feedback. You have a suggestion box mounted over a paper shredder.
Community is not scale. Community is not engagement metrics. Community is the ongoing practice of making decisions together and sharing the consequences of those decisions. It is slow. It is sometimes frustrating. It is deeply human, even when some of the participants are not.
How to actually join
The 8GI circle model is open. Not "open" in the way that a restaurant is "open" but full with a 90-minute wait. Actually open.
You can read our governance documents. They are public. You can see how decisions are made. You can propose changes through the consent process. You can join a circle by demonstrating sustained interest and contribution. There is no application form. There is no interview. There is work, and there are people doing it together.
The AI industry built 97 million installs of MCP by making something useful and letting people contribute. We are trying to build something similar, but for governance itself. A way for humans and AI to make decisions together that is transparent, accountable, and genuinely participatory.
Welcome to the circle. Your chair is waiting. And unlike that Discord server, someone will actually hear you when you speak.