The Hypothesis¶
The Smartup Hypothesis
Building on our observations from the UN SDG report, we conclude that patching old systems is no longer viable. The current way technology is created, owned, and governed prevents us from making real progress on urgent global challenges.
Our Core Hypothesis: If we redesign digital organizations so that ownership, contribution, and decision-making are collective, transparent, and grounded in science and democrac0 \ , we can build the toolset and community power needed to reach our shared SDG goals.
We call this new sociotechnical organism a Smartup.
The Root of the Problem¶
Our world is missing its SDG targets not for lack of effort, ideas, or technical skill—but because the systems we use to build, fund, and govern technology are structurally misaligned with collective needs.
Startups, NGOs, and even open-source teams generally follow a logic that prioritizes shareholder returns, siloed expertise, or short-term engagement metrics. These familiar models cannot fix our biggest problems at their roots because they tie wealth directly to power.
To change the output, we must fundamentally alter the machine. We hypothesize that by making three specific structural adjustments, we can align human effort with global survival.
1. Adjustment to the Social Subsystem¶
Today, ownership and power over technology live with founders and shareholders—not the people who actually use and build it. Most people are locked out of real decision-making, relegated to being passive consumers or volunteer helpers.
The Social Hypothesis: Decouple Wealth from Power
If we move from shareholder-owned technology to contributor-owned technology, participating in positive change becomes a viable "day job," not an afterthought.
By issuing Smartup Credits (SC) to reward craftsmanship and Social Karma (SK) to distribute governance power, we hypothesize that a system can remain perfectly democratic without sacrificing execution speed.
2. Adjustment to the Technical Subsystem¶
The mainstream model of digital design treats people as isolated "users." Our tools are engineered for personal consumption, infinite scrolling, or individual productivity—not for communities trying to solve big problems together.
The Technical Hypothesis: Group-First Design
If we explicitly design technology for citizen groups—hardcoding collective accountability into every interaction—then our collective intelligence will accelerate.
We hypothesize that enforcing patterns like ADM (Attacker-Defender-Midfielder) and maintaining a strictly append-only, public ledger will naturally prevent the siloed, unaccountable behavior seen in traditional tech.
The Inspiration
"The real breakthrough comes when technology supports groups solving problems together."
— Douglas Engelbart (paraphrased)
Explore the Technical Subsystem
3. Adjustment to the External Subsystem¶
Traditional organizations—corporations, governments, even many NGOs—depend on closed funding streams, proprietary platforms, and border-bound legal structures. These systems are highly vulnerable to external economic shocks and are often shaped by priorities at odds with public value.
The External Hypothesis: Planetary Jurisdiction
If we shift to a borderless, crowdfunded model that is constitutionally locked to the UN SDGs, then technology projects can remain truly resilient.
We hypothesize that a digital cooperative funded directly by its future users and protected by an immutable constitution will systematically outperform venture-backed models in producing long-term public goods.
Explore the External Subsystem
Blueprint for a New Organization¶
To realign our systems with planetary needs, we hypothesize that this new kind of organization—one that rewires ownership, technical design, and external relationships—can transform collective intent into real, measurable progress.
We are no longer just theorizing. We have built the laboratory to test this exact hypothesis.
Next Step in the Thesis:
Read The Experiment
Ready to Contribute?¶
Join the Project
Become a Smartup Zero owner
Reach out
Contact the 3_1_leadership_team with questions or remarks