NextStacks Design Principles
How we decide what belongs in our next self-governance toolkit
The social contract is being renegotiated, whether we wanted that or not. People across the political spectrum feel the old arrangements aren't working — and they're right. NextStacks is an effort to figure out, together and in the open, what the next set of working pieces looks like, and how communities can pick them up and try them without anyone forcing the issue.
Self-governance isn't an event every few years; it's an ongoing practice. These principles are for shaping that practice in fair and useful ways.
These are the seven things each piece has to clear.
1. Trust what works, for you and them.
A piece earns its place in the toolkit when it works for the people you'd never invite to dinner, not just the people you would. We're not going to settle who has the correct theory; we're going to look at what gets built when people who don't already agree decide to build something anyway. The toolkit is for everyone or it's for no one.
2. Testable locally, grows by use.
A piece should be testable by a real group at local scale — a council, a co-op, a congregation, a classroom — without permission from above. And it should be designed so the early version can grow into a mature practice through use, not get replaced by a "real" program later. The seed and the tree are the same organism.
3. It's a kit.
The pieces are designed to fit together, sit alongside each other, and be swapped without losing what you've built. A community shouldn't have to abandon what's working to try something new, and shouldn't lose its history, decisions, or memory when it changes pieces. The toolkit isn't a unified machine — it's a kit, and kits work because the pieces are made to come and go.
4. Boring plumbing, interesting results.
The mechanics should feel familiar. A meeting should still feel like a meeting. A vote should still feel like a vote. If the plumbing feels exotic, most people won't try it. The novelty lives in what comes out, not in how it looks going in.
5. Share what you learn — honestly, and with attribution.
What one community tries, every community can study. Successes, failures, half-measures, and surprises all go into a shared, durable record that anyone can read, search, and build on years later. Whoever does the work gets named. Whatever didn't go as planned gets written up honestly. We don't have to repeat each other's mistakes if we can read each other's notes.
6. Forkable without permission.
Anyone can take a piece, change it, rename it, run with it in a direction we wouldn't have chosen — and we celebrate that, not police it. We name the one thing that has to stay intact for the piece to still work, and everything else is yours to bend. Projects that can't be forked die with their founders; projects that can be forked outlive them.
7. Naturally contagious.
A piece of the toolkit should be so useful and appealing that groups want to try it without anyone pushing. Mandates breed resentment. Good tools spread by example.
What these principles aren't
They aren't a purity test. A piece that mostly clears the bar but stumbles on one principle is still worth trying — we just want to know which one, so we're honest about the risk.
They aren't neutral. They favor bottom-up over top-down, durability over novelty, modesty over grandeur. That's on purpose. The pieces of the old stack that are crumbling fastest are the ones that forgot these things.
They aren't fixed. If a community tries something and discovers an eighth principle we missed, the principles change. That's the whole idea.
What's next
If you've got a piece you think belongs in the next stack — a tool, a practice, a way of running a meeting, a way of holding money, a way of settling a fight — bring it. Tell us what it is, where it's been tried, what it's load-bearing on, and where it broke when it broke.
This is a conversation, not a manifesto.
Parking lot (not for this document — for the project)
Threads worth pulling on later:
- Stewardship and Ownership (not vs. — both, together). The rancher and the commons activist already practice stewardship; they just don't know they're allies.
- Shared and individual responsibilities. The both/and version of a debate that's been framed as either/or for forty years.
- Cross-community pattern-sharing. The toolkit gets exponentially more useful when communities can see each other's experiments side by side. The trust and curation problems that come with that are themselves NextStacks-shaped — the infrastructure that lets NextStacks learn across communities is itself something NextStacks would have to figure out.
- Everyone has a Them. The piece behind "Trust what works, for you and them." Why the renegotiation can't be done by half the country alone, and why every NextStack ultimately rests on this.
- Self-governance is something we do, not something that happens to us. The continuous-governance / long-term-memory post. Currently the single most differentiating idea in the project; deserves its own Nugget when ready.
- Where boundaries live in a connected mind. Meta-Nugget on how a Brain-shaped synthesizer carves bite-sized posts out of a network. Almost everyone in the audience has this problem.
- A complementary client-facing thread. Two or three Nuggets — kept structurally separate from the thesis sequence so neither contaminates the other — that address the business of living inside this thesis and what working together looks like for people who agree with the picture.
- The progressive critique stream. A parallel Nugget thread arguing that progressive/liberal/Lefty thinking and acting over recent decades has gone off the path, and what rethinking along NextStacks lines might look like. The risk to manage here is voice, not content: the difference between a critique from within (which lands) and a defection (which doesn't) is almost entirely how the love for the tradition comes through. Worth workshopping the voice carefully before publishing.