TL;DR
This thesis continues an investigation that is as old as computer science itself. It's a question that matters to all of us: despite computers getting smarter and smarter, why is it that we, as a group, often struggle to solve complex problems together, even when we share a deep concern about the outcome?
Our hypothesis is that it's not because people aren't smart enough. We think it's because the tools and structures around us were never designed to think and decide together as a group. Instead they have been created with the individual in mind. This is a study about how we can change that.
Although we strive to be as simple and straightforward as possible in our language, besides this summary page, the actual thesis itself will contain computer and science jargon that we rely upon to describe our findings as precisely as possible.
Introduction¶
Imagine you and your friends want to build something together: a community garden, a school project or a neighbourhood app. You're all of good will and intelligent in your own way. You all care. You all want to help. Conditions for collaboration seem perfect. You're off to a good start and yet, something always goes wrong. Someone's good idea gets forgotten. A decision made last month is repeated. People leave and take all their knowledge with them. Communication breaks down. The group slows down instead of speeds up.
You've probably noticed this happening everywhere: in schools, workplaces, volunteer organisations, cities trying to solve homelessness, or on a bigger scale: countries trying to address climate change.
Here's the strange part: We have made computers incredibly good at helping individuals. But we have barely figured out how to use technology to help groups think and work together.
This thesis asks: What if we deliberately designed systems to help communities become smarter at working together?
The Thesis in One View¶
graph TD
PROBLEM["THE PROBLEM <br/>Smart people in groups<br/>still struggle to learn,<br/>remember, and coordinate"]
HYPOTHESIS["THE HYPOTHESIS<br/>Three changes help:<br/>Real shared power<br/>Permanent group memory<br/>Community autonomy"]
APPARATUS["THE APPARATUS<br/>SmartupOS:<br/>A laboratory designed<br/>to test this fairly"]
EXPERIMENT["THE EXPERIMENT<br/>Smartup Zero:<br/>A real community building<br/>real technology, measured carefully"]
EVIDENCE["THE EVIDENCE<br/>Does it work?<br/>We're measuring and publishing<br/>everything openly"]
PROBLEM --> HYPOTHESIS
HYPOTHESIS --> APPARATUS
APPARATUS --> EXPERIMENT
EXPERIMENT --> EVIDENCEThe Problem We Observe¶
When communities try to solve complex problems, we see these patterns repeat:
A group makes a mistake. Years later, the same mistake happens again. Nobody remembered the lessons.
Why? Because the knowledge was scattered. Someone's email. Someone's notebook. And when people leave, the learning vanishes.
Decisions are made. But nobody can remember why they were made.
Why? Because the reasoning is locked in someone's head or buried in email threads.
A brilliant engineer, a thoughtful administrator, a creative artist—all in one group. But their different perspectives don't combine. Instead, they get in each other's way.
Why? Because systems are designed for one person working alone.
A group doesn't know who makes decisions. They don't know their own strengths and weaknesses.
Why? Because their own structure is invisible to them.
A threat appears on the horizon. Nobody notices until it's a crisis. An opportunity emerges. The group is too slow to grab it.
Why? Because information doesn't flow smoothly.
When funding disappears or external pressure increases, the group falls apart.
Why? Because they depend on external control and external money.
Our Hypothesis: What If We Changed Three Things?¶
graph TB
SOCIAL["1. REAL SHARED POWER<br/>Everyone votes<br/>Power earned through service<br/>Power shrinks if you stop helping"]
TECH["2. GROUP REMEMBERS<br/>Everything is recorded<br/>With the reasoning why<br/>New people can see all history"]
EXTERNAL["3. COMMUNITY AUTONOMY<br/>Funded by members<br/>Rules can't be secretly changed<br/>Tools are open-source"]
IMPROVEMENT["Together, these help:<br/>Learn faster<br/>Remember better<br/>Work together more smoothly<br/>Understand themselves<br/>Respond to threats<br/>Make better plans<br/>Coordinate efficiently"]
SOCIAL --> IMPROVEMENT
TECH --> IMPROVEMENT
EXTERNAL --> IMPROVEMENTThe Experiment: How we test the hypothesis and measure results¶
We have a real group of people: Smartup Zero.
They are building a real technology: an emergency communication system called ONLIFE.
And we are watching, very carefully, whether these three changes actually help them become more collectively intelligent. We've built a laboratory for that: SmartupOS
We're not guessing. We're measuring.
| What We Measure | How We Know It's Working |
|---|---|
| Do they learn faster? (Indicator 1: Learning) | New ideas build on old ones instead of repeating |
| Do they remember better? (Indicator 2: Memory) | New members understand history faster |
| Do different perspectives integrate? (Indicator 3: Integration) | More people contribute together on problems |
| Do they understand themselves? (Indicator 4: Self-Understanding) | Structure on paper matches actual function |
| Do they perceive their environment clearly? (Indicator 5: Perception) | They spot changes and opportunities sooner |
| Do they respond to threats faster? (Indicator 6: Threat/Opportunity Recognition) | Crisis detection time decreases |
| Are their plans better? (Indicator 7: Planning) | They execute with less rework |
| Do they coordinate smoothly? (Indicator 8: Coordination) | Tasks complete faster with less conflict |
The key idea: We're not asking people "do you feel like you work together better?" We're watching what actually happens and measuring it.
The Laboratory: The software we built to run the experiment in a controlled environment¶
To run this experiment fairly, we built our own laboratory apparatus called SmartupOS.
Think of it like this: If you wanted to study how plants grow under different conditions, you wouldn't use a random garden. You'd build a controlled greenhouse where you could measure everything precisely.
SmartupOS is our greenhouse for studying Collective IQ within groups that have a shared mission.
-
Element / Matrix
Where people talk and give commands.
Like a chat room, but owned by the group (not a corporation), designed to keep focus instead of distraction.
-
Engelbot
Where commands happen.
When someone types
!start_workor!complete_task, the system understands and makes it happen. No need to be a programmer. -
Forgejo
Where truth lives.
A permanent record of everything. Every decision, every task, every transaction. In plain text anyone can read. With complete history.
-
Serverside
Where it runs.
Hosted in Europe, owned by the community, not any corporation. If we needed to move it tomorrow, we could.
The Reading Path¶
This thesis has five main chapters. Read them in order if you wish to take the deep dive. If you know enough for now and just want to help or participate, scroll down.
-
1. The Observation
What are we seeing in the world? Why do groups struggle? What are the specific problems?
Read time: 10 minutes
-
2. The Hypothesis
What if we could fix these problems? Here's our three-part idea. Here's why we think it could work.
Read time: 12 minutes
-
3. The Methodology
How do we make sure we're testing this fairly? How do we avoid fooling ourselves? How can others repeat our experiment?
Read time: 15 minutes
-
4. The Experiment
What does the actual test look like? Who is involved? What are we measuring?
Read time: 12 minutes
-
5. The Laboratory
A detailed look at SmartupOS. How it's built. Why we built it this way. How it enables fair measurement.
Read time: 15 minutes
Ways to Participate¶
-
Join Smartup Zero
Become an participant in the first experiment.
-
Start Your Own Smartup
Take SmartupOS and run your own experiment.
-
Sponsor the Research
Support Timeline0 and Smartup Zero through funding.
-
Collaborate as Researcher
Work on the research programme itself.
Current Status¶
🟠 Phase: Pre-Validation (Building & Testing the Laboratory)
| What's Running | Purpose |
|---|---|
| Element/Matrix | ✅ All team communication happening here |
| Engelbot | ✅ Commands executing safely |
| Forgejo Ledger | ✅ Complete audit trail being kept |
| Measurement System | ✅ Baselines being established |
Next: Expand to full Validation Phase with more participants.
Start Reading
Begin with The Observation. It explains the problem in concrete terms you can recognise from your own life.
Then read through in order. Each section builds on the last.
Total reading time: about 1 hour for the whole thesis.
Questions?¶
This thesis is written to be understood. If something is unclear, that's our fault, not yours.
Contact us to ask questions.