Governance Process: Community Decision-Making and Stewardship
How We Guide the Protocol Together
"I am because we are" β Ubuntu
Introduction
UBEC isn't governed by a corporation or a small group of founders. It's governed by youβthe community of token holders, farmers, communities, activators, and living labs who participate in the ecosystem.
This guide explains how decisions are made, how you can participate, and how we ensure that governance reflects Ubuntu principles.
Governance Philosophy
Ubuntu-Centered Decision Making
Traditional governance often assumes: - Decisions benefit some at others' expense - Power should be concentrated for efficiency - Majority rule is sufficient legitimacy - Speed matters more than wisdom
Ubuntu governance operates differently: - Decisions should benefit everyone β We seek outcomes where all stakeholders gain - Power should be distributed β No single entity controls the protocol - Consent, not just majority β We seek decisions no one strongly opposes - Wisdom over speed β Good decisions take the time they need
The Three Pillars of UBEC Governance
π± 1. Subsidiarity
Decisions should be made at the lowest appropriate level. A bioregion shouldn't decide what a single farmer decides. The global protocol shouldn't decide what bioregions can decide for themselves.
π 2. Participation
Everyone affected by a decision should have voice in that decision. Governance isn't something that happens to youβit's something you do.
π 3. Stewardship
Governance isn't ownership. Those who govern are stewards, not owners. We make decisions on behalf of future generations, not just current participants.
Governance Structure
Three Levels of Decision-Making
UBEC governance operates at three nested levels:
βββββββββββββββββββββββββββββββββββββββββββ
β π Protocol Level β
β System-wide rules & parameters β
βββββββββββββββββββββββββββββββββββββββββββ
β
βΌ
βββββββββββββββββββββββββββββββββββββββββββ
β ποΈ Bioregional Level β
β Local implementation & priorities β
βββββββββββββββββββββββββββββββββββββββββββ
β
βΌ
βββββββββββββββββββββββββββββββββββββββββββ
β π€ Participant Level β
β Individual choices & contributions β
βββββββββββββββββββββββββββββββββββββββββββ
Protocol-Level Governance
What Gets Decided at Protocol Level?
- Token economics (supply, distribution ratios)
- Core algorithm parameters (holonic scoring weights)
- New bioregion approval
- Protocol upgrades and technical changes
- Inter-bioregional policies
- Emergency responses to system-wide issues
The Protocol Council
The Protocol Council is responsible for protocol-level decisions. It consists of:
| Role | Count | Selection Method |
|---|---|---|
| Bioregion Representatives | 1 per active bioregion | Elected by bioregion members |
| Beneficiary Type Representatives | 4 total | 1 each for Farmers, Communities, Activators, Living Labs |
| Technical Stewards | 3 | Selected for technical expertise |
| Ubuntu Elders | 2 | Recognized for wisdom and Ubuntu practice |
Term: 12 months with staggered rotation
Meetings: Monthly, with special sessions as needed
Decisions: Consent-based (no strong objections)
Proposal Process
Anyone can submit a proposal for protocol-level change:
Step 1: Draft Proposal
Write a proposal including: - Problem statement: What issue does this address? - Proposed solution: What specific change do you propose? - Impact analysis: How will this affect different stakeholders? - Ubuntu alignment: How does this reflect Ubuntu principles? - Implementation plan: How would this be executed?
Step 2: Community Discussion
- Proposal posted to governance forum
- 14-day discussion period
- Amendments and refinements based on feedback
- Seek to address all concerns raised
Step 3: Consent Check
- Council reviews refined proposal
- Members indicate: Support / Accept / Object
- Support: I actively endorse this
- Accept: I can live with this
- Object: I have a serious concern that must be addressed
If objections exist, return to discussion. Seek to integrate all perspectives.
Step 4: Implementation
- Approved proposals move to implementation
- Technical stewards oversee execution
- Progress reported to community
- Post-implementation review
Bioregional-Level Governance
What Gets Decided at Bioregional Level?
- Local economic priorities
- Membership criteria and processes
- Internal resource allocation
- Local partnerships and collaborations
- Environmental monitoring approaches
- Cultural protocols and practices
Bioregional Assembly
Each bioregion has its own governance body:
- Composition: All active participants in the bioregion
- Meetings: At least quarterly, more often as needed
- Decision method: Determined by each bioregion (consent, consensus, or voting)
Flexibility Within Framework
Bioregions have significant autonomy to: - Define their own governance structures - Set local priorities and focus areas - Establish cultural protocols - Design onboarding processes - Create local working groups
However, bioregions must operate within protocol parameters: - β 75/20/5 distribution ratios - β Holonic evaluation principles - β Ubuntu values alignment - β Transparency and accountability - β Participation in protocol governance
Participant-Level Governance
Your Governance Rights
As a UBEC participant, you have the right to:
β
Voice β Share your perspective on any decision
β
Vote β Participate in bioregional decisions
β
Propose β Submit proposals at any level
β
Elect β Choose your bioregional representatives
β
Object β Raise concerns about decisions affecting you
β
Exit β Leave the system if you disagree fundamentally
Your Governance Responsibilities
With rights come responsibilities:
π Stay informed β Follow governance discussions
π¬ Participate β Contribute your voice to decisions
π€ Listen β Genuinely consider others' perspectives
π± Ubuntu lens β Seek outcomes that benefit everyone
β° Show up β Attend meetings and participate actively
Holonic Level and Governance
Your holonic category affects your governance participation:
| Category | Governance Role |
|---|---|
| βͺ Observer | Can observe, comment, and learn |
| π Participant | Full voting rights in bioregion |
| π΅ Contributor | Can serve on working groups |
| π’ Integrator | Eligible for representative roles |
| π£ Exemplar | Eligible for Protocol Council |
Decision-Making Methods
Consent-Based Decision Making
UBEC's default decision method is consent, not consensus or majority vote.
Consensus asks: "Does everyone agree?"
Majority vote asks: "Do most people agree?"
Consent asks: "Can everyone live with this?"
The key question in consent: "Do you have a reasoned objection?"
An objection is valid if: - It identifies harm that would result - It's based on the proposal itself (not personal preference) - It relates to the group's purpose and values - The objector can articulate the concern clearly
When to Use Different Methods
| Situation | Recommended Method |
|---|---|
| Major protocol changes | Consent with extended discussion |
| Routine operational decisions | Working group decision |
| Time-sensitive issues | Designated decision-maker with accountability |
| Resource allocation | Consent or voting depending on bioregion |
| Conflict resolution | Mediated dialogue seeking consent |
Governance Tools and Interfaces
Digital Governance Platform
UBEC provides tools for governance participation:
π Proposal System - Submit and track proposals - Participate in discussions - Record decisions
π³οΈ Voting Interface - Cast votes on bioregional matters - View results and participation rates - Track your voting history
π Governance Dashboard - See upcoming decisions - Review past decisions - Track implementation progress
π¬ Discussion Forums - Threaded discussions on proposals - Working group spaces - Cross-bioregional dialogue
Accessing Governance Tools
- Log in to your UBEC dashboard
- Navigate to "Governance" section
- See active proposals and upcoming votes
- Join relevant working groups
- Track your participation history
Special Governance Processes
Emergency Decisions
Some situations require faster response:
Definition of Emergency: - Immediate threat to system integrity - Security vulnerability discovered - External regulatory requirement - Force majeure events
Emergency Process: 1. Technical stewards identify emergency 2. Temporary measures implemented (max 72 hours) 3. Emergency Protocol Council meeting called 4. Community notified within 24 hours 5. Ratification vote within 7 days
Conflict Resolution
When conflicts arise:
Level 1: Direct Dialogue - Parties communicate directly - Seek mutual understanding - Find Ubuntu-aligned resolution
Level 2: Mediation - Neutral mediator facilitates - Focus on underlying needs - Seek win-win solutions
Level 3: Bioregional Panel - Panel of peers reviews situation - Recommends resolution - Binding within bioregion
Level 4: Protocol Arbitration - For inter-bioregional conflicts - Protocol Council appoints arbitrators - Final and binding decision
Constitutional Amendments
The most fundamental rules require special process:
- Affects: Core Ubuntu principles, basic rights, fundamental structure
- Threshold: 2/3 of Protocol Council + majority of bioregions
- Process: Extended discussion (minimum 60 days) + ratification period
- Cooling off: 30-day implementation delay for reconsideration
Distribution Governance
The 75/20/5 Rule
All token distributions follow: - 75% to community participants - 20% to reserve fund - 5% to operations
This ratio is constitutionalβchanging it requires the amendment process.
Monitoring Compliance
The system automatically: - Tracks actual distribution percentages - Flags deviations from targets - Recommends corrective actions - Reports to governance bodies
Reserve Fund Governance
The 20% reserve is governed by: - Designated reserve stewards - Clear spending criteria - Community approval for disbursements - Annual audit and reporting
Participation Rewards
Governance Participation Matters
Your governance participation contributes to your holonic score:
Activities that count: - Attending bioregional assemblies - Voting on proposals - Participating in discussions - Serving on working groups - Contributing proposals - Mediating conflicts
Recognition Without Concentration
Governance participation is rewarded, but: - No governance position grants extra tokens - Influence comes from participation, not accumulation - Rotating leadership prevents entrenchment - Ubuntu values balance, not power accumulation
Getting Involved
Start Where You Are
- Attend your next bioregional assembly
- Read pending proposals on the governance platform
- Join a working group that interests you
- Share your perspective in discussions
- Propose something that would improve the system
Working Groups to Join
- π Policy Working Group β Develops proposals
- π± Onboarding Working Group β Welcomes new participants
- π» Technical Working Group β Reviews technical changes
- π Education Working Group β Creates learning materials
- π Sustainability Working Group β Environmental focus
- π€ Community Working Group β Relationship building
Resources
- Governance Forum: community.ubec.network
- Proposal Templates: Available in your dashboard
- Facilitation Guides: For running effective meetings
- Decision Records: Archive of past decisions
Governance Calendar
Regular Rhythm
| Frequency | Event |
|---|---|
| Weekly | Working group meetings |
| Monthly | Protocol Council meeting |
| Quarterly | Bioregional assemblies |
| Annually | Global UBEC gathering |
| Ongoing | Proposal discussions |
Key Dates
Check your dashboard for: - Upcoming votes and deadlines - Assembly meeting dates - Working group schedules - Proposal discussion periods
Principles for Good Governance Participation
π― Come Prepared
Read materials before meetings. Understand what's being decided. Bring informed perspectives.
π Listen First
Seek to understand before being understood. Others' perspectives may illuminate what you don't see.
π± Think Ubuntu
Ask: How does this benefit everyone? Where are the win-win possibilities? Who isn't being heard?
β° Respect Time
Be punctual. Be concise. Make space for others to contribute.
π Accept Evolution
Governance is never finished. What works today may need adjustment tomorrow. Stay flexible.
π€ Trust the Process
Even when decisions don't go your way, trust that good process leads to good outcomes over time.
Conclusion
UBEC governance is an ongoing experiment in Ubuntu-centered collective decision-making. It won't be perfectβbut it will be ours.
Your participation matters. Your voice matters. Your perspective is needed.
Together, we're not just governing a protocol. We're demonstrating that economics can be organized around relationships, reciprocity, and regeneration.
Welcome to the governance community. The decisions we make together shape the world we're building.
Attribution
This document was developed with the assistance of Claude and Anthropic PBC. The UBEC Protocol Suite uses the services of Claude and Anthropic PBC to inform decisions and recommendations.
UBEC DAO Protocol | Ubuntu Bioregional Economic Commons
Building regenerative economies rooted in relationship
Version 1.0 | December 2025