Collective Intelligence Network Get involved

Get involved

Find your part.

You don't have to build AI to help decide how it treats people. A city councillor, a safety researcher, a lab engineer and a parent can each do something real right now. Pick the path that fits your life.

Think of how a town keeps its drinking water clean or its streets safe for children walking to school. It never rests on one hero in a laboratory. The chemist tests the water sample, the plumber fits the valve, the town council writes the plumbing code, and the parent notices when a hydrant is leaking on the corner.

Keeping AI understandable and accountable works the same way. Each role holds a piece of the puzzle that nobody else can reach alone.

Policy makers

For officials, staffers and regulators who want practical procurement rules, plain-language briefings and honest evidence.

Researchers

For people working on AI safety, alignment, governance or collective intelligence who can test our assumptions and point out what we've missed.

AI labs

For researchers, engineers, safety teams and policy staff inside labs who want outside scrutiny and shared safety standards.

Builders

For engineers and open-source developers who want to turn ideas like verifiable receipts into working tools people can inspect.

Civil society

For co-operatives, credit unions, worker associations, tenant organisers and community clinics defending collective self-determination.

Everyone

For citizens, parents, workers, co-ops, unions, newsrooms and neighbours who want AI that answers to the people it affects.

How the five roles reinforce each other

Often, people in one role feel stuck because they are waiting on someone else. A policy staffer worries that requiring receipts on AI actions might be technically impossible. An engineer inside a lab knows receipts are easy to build, but worries management won't prioritise them unless customers and procurement officers ask for them.

When each group takes one practical step in the open, the logjam breaks:

  • Builders prove a safeguard works in clean, open-source code so nobody can claim it is impossible.
  • Researchers test that safeguard under adversarial pressure to find where it bends or breaks.
  • Lab teams adopt shared workload identities and receipt formats so safety doesn't punish the first mover.
  • Policy makers write those proven receipts and appeal rights into public procurement contracts.
  • Citizens, clinics, co-ops, and unions ask a simple question before adopting any tool: who does this assistant answer to, and can we see the receipt?
The Five Roles Civic Reinforcement Cycle A five-stage feedback loop showing how Builders, Researchers, AI Labs, Policy Makers, and Citizens reinforce each other to create accountable artificial intelligence. THE REINFORCEMENT CYCLE No single group solves this alone. Every practical step unblocks the next. 1. BUILDERS Clean Open-Source Code Proves safeguards work in testable code 2. RESEARCHERS Adversarial Audits Stress-tests failure boundaries 3. LAB TEAMS Shared Identity Standards Embeds scoped leases & receipts 4. POLICY MAKERS Procurement Levers Requires receipts in public rules 5. CITIZENS Democratic Demand Asks who assistants serve
The civic reinforcement cycle: each role provides the essential ground that makes the next step possible, turning isolated efforts into an enduring public safeguard.

Where things honestly stand

We are at the beginning of this work. Rather than oversell what we have, we want to be plain with you about what is ready today and what isn't.

Open now

  • Hard questions and critique of our work
  • Collaboration on open research problems
  • Pointers to prior work or things we've missed
  • Early review of drafts before we publish them
  • Interactive exploration in Shared Horizon and the Observatory

Not yet

  • Consumer desktop software to download or install
  • Donations, grants or outside investment
  • Open jobs or paid roles
  • Anything for sale, including tokens (we will never sell those)

If you don't fit neatly into any box above, write to us anyway at contact@collectiveintelligencenetwork.org. A person reads every message, and the best insights often come from people living with these systems firsthand.