Regen Commons

The Regen Commons Constitution

MVP constitution · text as of 11 November 2026

The governing agreement of the commons: why it exists, how it is organized, who holds which responsibilities and the protocols it follows. A short summary in plain words comes first, then the full text.

Context

Regen Commons emerges in a moment when humanity faces intertwined ecological, social, and cultural crises that demand more than isolated solutions. While many individuals, organizations, and communities are already working toward regenerative futures, their efforts are often fragmented, under-resourced, or constrained by systems built on extraction and competition.

Regen Commons is a response to this need: a common ground where resources can be pooled and stewarded collectively in service of regenerative action. It is not itself the site of every action, but rather the enabling infrastructure — a cooperative field that supports diverse communities and activities to thrive by directing common pool resources toward their regenerative efforts.

This document — the organizational DNA and Constitution of Regen Commons — defines the identity, structure, and protocols that guide how Regen Commons operates. It articulates the shared understanding we hold, the roles we play, and the agreements we use to align around a life-centered ethos. In doing so, it provides coherence without control, ensuring that Regen Commons remains an open, evolving, and trustworthy foundation for self-organized collective stewardship.

Freedom To Participate

You are free to take any action that fulfills the Purpose of the organization and the Roles that you hold - as long as you do not violate any Protocols; and you uphold the Values and Principles of this Constitution.

Identity

About

Metadata + Instructions
id
regen-commons-vision
name
Vision
description
A concise definition of what Regen Commons is, why it exists, and the unique role it plays.
temporal focus
Present-facing (anchored in current identity and commitments)
scope
Organizational essence (who we are, what we do, how we hold ourselves)
function
Establish clarity of identity and invite others into resonance and relationship
test
If someone new read this, they would immediately know whether Regen Commons is “for them.”

Short Form (one liner)
Regen Commons is common ground where members pool resources to support regenerative collective action.

Long Form (paragraph)

Regen Commons exists to provide the common ground for pooling and stewarding resources that support regenerative collective action. Rather than being the site of the work itself, the Commons enables it — gathering contributions of knowledge, capital, and care into a shared resource base that members can draw from. By holding these resources in trust and directing them toward regenerative efforts, Regen Commons strengthens the conditions for diverse communities and ecosystems to thrive.

Vision

Metadata + Instructions
id
regen-commons-vision
name
Vision
description
The world we seek to help create
temporal focus
Future-facing
scope
Global or systemic context
function
Inspiration and direction
test
If this came true, the organization might no longer be needed.

Regenerative culture, ecology, and economy flourish together as a coherent movement, grounded in shared commons where individuals and organizations pool resources to coordinate action.

Purpose

Metadata + Instructions
id
regen-commons-purpose
name
Purpose
description
Why we exist now.
temporal focus
Present (ongoing commitment), Timeless and unbounded by success metrics.
scope
Organizational identity and function, rooted in your Philosophy of what is good and valuable.
function
Core reason for being, attractor it draws people, energy, and coherence over time.
test
This would remain true even if our form evolves.

Regen Commons provides the common ground for individuals and organizations to pool resources, steward shared identity, and strengthen the foundations for coordinated regenerative action.

Mission

Metadata + Instructions
id
regen-commons-mission
name
Mission
description
What we do to fulfill our purpose.
temporal focus
Strategic, Translates purpose into a present-tense strategy.
scope
Operational, is achievable and measurable (though not necessarily limited to numbers). Exists within constraints—funding, capacity, regulatory environments. Can evolve or be updated in response to new information.
function
Describes how the purpose is enacted now
test
It might change every few years — it's how the purpose is pursued today.

Develop and maintain commons-based governance, recognition, and licensing systems that enable individuals and organizations to pool resources and coordinate regenerative action.

Values

Metadata + Instructions
id
regen-commons-values
name
Values
description
What we stand for.
temporal focus
Present and continuous
scope
Guides internal conduct, cultural tone, and ethical posture.
function
Shapes behavior, design decisions, and protocols at all levels.
test
If this value was violated, the organization would feel out of integrity — even if its mission was achieved
  • We value care as a grounding responsibility to people, place, and planet.
  • We value stewardship as a responsibility that transcends ownership or control.
  • We value transparency as a practice of creating clarity and openness in decisions and processes.
  • We value reciprocity as a commitment to ensuring benefits flow back to those who nurture the commons.
  • We value plurality as an honoring of many expressions of regenerative practice while sustaining coherence.
  • We value collaboration as trust in the power of collective intelligence and coordinated action.
  • We value integrity as a commitment to prioritizing what is right for the commons over expedience or control.

Mandates

Metadata + Instructions
id
regen-commons-mandates
name
Mandates
description
A clearly defined area of responsibility the organization is committed to upholding through its roles, actions, and structures.
temporal focus
Present and continuous
scope
Defines the organization’s functional responsibility
function
Guides strategic focus, resource allocation, role design, and partnership alignment
test
If this mandate were abandoned or neglected, the organization would no longer be fulfilling its reason for existing — even if other work continued.
  • Steward Regen resources as a shared commons.
  • Maintain transparent protocols for membership, funding, and resource use that support collective trust.
  • Curate, protect, and activate shared resources so they generate value for the whole.
  • Enable recognition of contributions and reciprocal value flows across diverse archetypes and participants.
  • Facilitate collaborative processes and spaces that align efforts and allow new forms of coordination to emerge.
  • Safeguard legitimacy through accountable governance, cultural integrity, and conflict transformation.

Worldview

Metadata + Instructions
id
regen-commons-worldview
name
Worldview
description
A core worldview or system of understanding that informs how the organization relates to life, place, and purpose.
temporal focus
Foundational and enduring
scope
Informs values, ethics, design, governance, and cultural coherence
function: Grounds decisions and direction in a deeper cosmology or way of seeing the world
function
Guides strategic focus, resource allocation, role design, and partnership alignment
test
If this philosophy were removed or violated, the organization’s identity and integrity would be fundamentally altered — even if its activities remained the same.

Regenerative (“Regen”) identity describes a life-centered approach to organizing human and ecological systems in ways that restore, renew, and evolve the capacity of life to thrive in abundance across time.

It goes beyond sustainability (maintaining the status quo) toward reciprocity and flourishing: not just reducing harm, but actively repairing what has been degraded, strengthening resilience, and creating conditions for planetary well-being.

In practice, being regenerative means designing economies, cultures, and governance structures that produce dynamic equilibrium between human and natural systems through alignment with living-systems principles, and embed justice, equity, cohesion, belonging, trust, consent and interconnection at each level and scale of interaction.

Regen is both a worldview and a practice:

  • A worldview that shifts from extraction to reciprocity, from scarcity to abundance, from isolated fixes to whole-systems flourishing.
  • A practice of cultivating relationships, institutions, and infrastructures that center care for people, place, and planet.

Principles

Life-Centered Stewardship

Place the flourishing of life — human and more-than-human — at the center of decisions, designs, and actions.

Strong adherence
Prioritizing life-supporting outcomes in all decisions, even if it means reduced profit, slower timelines, or added complexity.
Weak adherence
Using environmental or social considerations as one of several factors, but still centering growth or efficiency.
Strong violation
Actively exploiting people or ecosystems for gain, disregarding well-being entirely.
Weak violation
Overlooking ecological or human impacts in minor decisions (e.g., using extractive suppliers without due diligence).

Whole-Systems Thinking

Work across ecological, social, cultural, and economic dimensions as interconnected parts of one living system.

Strong adherence
Consistently designing with feedback loops and interdependencies in mind, seeking holistic outcomes.
Weak adherence
Occasionally recognizing system linkages, but treating domains (e.g., finance, ecology) as mostly separate.
Strong violation
Designing deliberately siloed, linear, or extractive systems that cause cascading harms.
Weak violation
Ignoring cross-system effects (e.g., ecological harm hidden by financial gains).

Reciprocity & Renewal

Ensure that flows of value, energy, knowledge, and resources give back more than they take, fostering ongoing renewal rather than depletion.

Strong adherence
Embedding reciprocity into all exchanges, ensuring surplus for people, places, and ecosystems.
Weak adherence
Giving back occasionally (e.g., donations, offsets, energy), but not proportionally or systemically.
Strong violation
Extracting resources, labor, or culture without giving back, leaving lasting depletion.
Weak violation
Taking more than is given in small ways (e.g., underpaying contributors, neglecting replenishment).

Equity & Justice

Recognize and honor diverse ways of knowing, being, and belonging. Commit to fair and just participation in regenerative futures.

Strong adherence
Centering equity in governance, redistributing resources, and embedding justice structurally.
Weak adherence
Including marginalized voices occasionally, but without shifting power or resources.
Strong violation
Excluding, exploiting, or actively marginalizing vulnerable groups.
Weak violation
Overlooking equity in decisions, tokenizing participation.

Relational Wealth

Value trust, connection, and community as forms of wealth as essential as financial capital.

Strong adherence
Actively cultivating trust, reciprocity, and community bonds as the foundation of work.
Weak adherence
Naming relationships as important, but treating them as secondary to transactions.
Strong violation
Exploiting relationships for gain, sowing distrust, or eroding community fabric.
Weak violation
Breaking small commitments, neglecting community care.

Resilience & Adaptability

Design for flexibility, diversity, and adaptive capacity, ensuring continuity across generations.

Strong adherence
Building redundancy, diversity, and adaptive feedback loops into every system.
Weak adherence
Having contingency plans but not integrating resilience deeply into operations.
Strong violation
Creating rigid systems that collapse under stress, harming people or ecosystems.
Weak violation
Ignoring signals of change, relying on brittle or centralized solutions.

Movement Building

Act in ways that strengthen collective capacity — linking individuals, communities, and institutions into a regenerative movement greater than the sum of its parts.

Strong adherence
Sharing resources, knowledge, and infrastructure to grow collective capacity and alignment.
Weak adherence
Participating in networks but prioritizing individual visibility or outcomes.
Strong violation
Fragmenting movements through competition, co-optation, or extraction of legitimacy.
Weak violation
Withholding contributions, failing to acknowledge interdependence.

Participation & Co-Creation

Invite broad participation and distributed agency, trusting in collaborative intelligence to shape regenerative outcomes.

Strong adherence
Distributing decision-making power and trusting collective processes.
Weak adherence
Inviting participation but retaining central control over decisions.
Strong violation
Actively excluding stakeholders, enforcing top-down control, suppressing co-creation.
Weak violation
Limiting participation to surface-level input, ignoring community wisdom.

Abundance Mindset

Operate from the understanding that regeneration produces more possibility and vitality, not less, cultivating cultures of thriving rather than scarcity.

Strong adherence
Designing systems that unlock shared value, cultivating cultures of generosity and thriving.
Weak adherence
Using abundance language but still acting from fear of scarcity.
Strong violation
Operating from fear and zero-sum extraction, perpetuating scarcity culture.
Weak violation
Hoarding resources, failing to share knowledge or opportunity.

Structure

Components

The fundamental categories and building blocks we use to name, organize, and relate to our structure. This section defines the core components within the Commons' operational reality.

Asset

Metadata
id
RC-asset-TYPE-###
name
null
description
null
assetType
null
relatedMembranes
null
relatedProtocols
null
relatedAssets
null
location
null

This object defines an asset owned or managed by the Commons. Assets can be financial, digital, reputational, or intellectual property. Each asset is stewarded by one or more roles and governed by specific protocols.

Membrane

Metadata
id
RC-membrane-###
name
null
description
null
type
null
relatedProtocols
null
relatedMembranes
null
parentMembranes
null
childMembranes
null
relatedAssets
null
relatedRoles
null
sameAs
null
workSpaceLink
null

Boundaries that regulate participation, permissions, and trust thresholds.

Membranes are semi-permeable boundaries that define coherent units of action, intention, and collaboration. Each membrane has entry/exit criteria, maintains appropriate internal governance, is accountable to values and protocols, and can steward its own subset of assets, roles, and responsibilities.

Role

Metadata
id
RC-role-###
name
null
description
null
relatedMembranes
null
relatedAssets
null
relatedProtocols
null
criteria
null
responsibilities
null
benefits
null
roleAddress
null
isActive
null

Containers of agency and responsibility within the organization.

This object defines a role within the Commons. Roles are distinct sets of responsibilities and permissions that can be held by members. They are the building blocks of the organization's structure.

Protocol

Metadata
id
RC-protocol-###
name
null
description
null
initializationEvent
null
associatedFunctions
sense-making, decision making, resource allocation, coordination, learning, culture
associatedRoles
null
relatedMembranes
null
steps
null

The core life processes required to sustain and evolve the organism.

This object defines a protocol, which is a repeatable, documented process for coordinating action within the Commons.

Roles

Member

Metadata
id
RC-role-member
name
Member
description
Certified commoner with baseline governance rights and responsibilities.
relatedMembranes
Community Assembly
relatedAssets
Constitution
relatedProtocols
Member Protocol, Decision-Making Protocol
criteria
Verified alignment with Purpose and Values; invitation and consent per Member Protocol.
responsibilities
Participate in governance; uphold values; peer accountability; vote on proposals within scope.
benefits
Voting rights; ability to propose projects; access to member-only resources.
roleAddress
Hats role (TBD)
Role
Certified commoner with baseline governance rights and responsibilities in the MVP community.
Benefits
Voting rights on proposals; ability to propose projects; access to member-only Resources and Assets; participation in assemblies.
Rights
Equal voting rights; seek advice or consent on proposals; access governance records; fair process in advancement and exit.
Responsibilities
Participate in votes and discussions; uphold Values; peer accountability, including monitoring conditions of use of commons brand and assets; follow protocols; disclose conflicts of interest; contribute to shared learning where relevant.

Gardener

Metadata
id
RC-role-gardener
name
Gardener
description
Tends, cultivates, and cares for shared resources and relationships; curates knowledge, supports culture, and maintains health/abundance signals across the commons.
relatedMembranes
Community Assembly, Project
relatedAssets
Core IP, Governance Forum, Brand Assets
relatedProtocols
Publishing Protocol, IP Protocol, Decision-Making Protocol, Conflict Transformation Protocol
criteria
Alignment with Purpose and Values; demonstrated caretaking/curation skills; trusted participation record; willingness to steward cultural and knowledge assets.
responsibilities
Curate and organize resources; maintain documentation and metadata quality; support community rituals and communications; monitor health/abundance metrics; facilitate feedback and learning loops; uphold brand and knowledge integrity.
benefits
Recognition for care labor; access to curation tools and support; eligibility for funded scopes; attribution for contributions.
roleAddress
Hats role (Gardener) (TBD)
isActive
true
Role
Cultural and knowledge steward who tends the commons’ resources, documentation, and relationships to keep them healthy, accessible, and legitimate.
Benefits
Recognition and attribution for care labor; access to curation and collaboration tools; potential funded scopes via project proposals; visibility in Governance Forum as resource maintainer.
Rights
Propose curation standards and improvements; request access needed for metadata and publishing; raise care/legitimacy concerns; initiate advice processes for resource changes.
Responsibilities
Curate and maintain knowledge and brand resources; publish updates and changelogs; help facilitate community communications/rituals; track and report health/abundance indicators; ensure compliance with Publishing, IP, and Brand protocols; support conflict transformation through documentation and context.

Operator

Metadata
id
RC-role-operator
name
Operator
description
Operates core commons infrastructures, facilities, programs, and core infrastructure management, maintenance, and operations.
relatedMembranes
Operations Team
relatedAssets
Commons Treasury Multi-Sig, Governance Forum
relatedProtocols
Operator Protocol, Treasury Management Protocol, Decision-Making Protocol
criteria
Demonstrated operational skills; alignment with Purpose and Values; capacity for ongoing infrastructure work; approved by Operations Team.
responsibilities
Maintain and operate core infrastructure; manage facilities and programs; coordinate operational work streams; report on infrastructure status.
benefits
Compensation for operational work; access to operational tools and resources; recognition for infrastructure contributions.
roleAddress
Hats role (TBD)
isActive
true
Role
Individual who contributes to ongoing work streams related to commons facilities, programs, or core infrastructure management, maintenance, and operations.
Selection
Application or nomination to Operations Team; assessment of operational skills and capacity; approval by Stewards; role credentialed (Hats) with defined scope and responsibilities.
Requirements
Demonstrated operational skills and experience; alignment with Purpose and Values; capacity for ongoing infrastructure work; commitment to operational protocols and reporting.
Benefits
Compensation for operational work; access to operational tools and resources; recognition for infrastructure contributions; participation in operational planning and decision-making.
Rights
Access to necessary operational tools and data; propose operational improvements; request resources for infrastructure work; fair recognition of contributions.
Responsibilities
Maintain and operate core infrastructure; manage facilities and programs; coordinate operational work streams; report on infrastructure status and needs; follow operational protocols and safety standards.

Licensed Partners

Metadata
id
RC-role-licensed-partner
name
Licensed Partner
description
Organization using Regen brand under lightweight licensing agreements.
relatedMembranes
Community Assembly
relatedAssets
Brand Assets
relatedProtocols
Brand Usage Protocol
criteria
Values alignment assessment; license approval per protocol.
responsibilities
Adhere to brand guidelines; contribute back via fees/stories; uphold legitimacy.
benefits
Brand usage rights; community recognition; access to shared resources.
roleAddress
Access credential/NFT (TBD)
Role
External organization granted rights to use Regen brand assets under a lightweight license.
Benefits
Brand legitimacy and recognition; access to guidance/templates; optional inclusion in public directory; participation in aligned campaigns.
Rights
Use Regen brand within the scope/territory set by the license; appeal or request review/modification of terms; receive due process before revocation.
Responsibilities
Adhere to guidelines; maintain legitimacy and quality; report usage and outcomes; contribute back per terms (fees/stories/attribution); accept revocation if misuse is not resolved.

Project Participant

Metadata
id
RC-role-project-participant
name
Project Participant
description
Regen Commons member or non-member contributing to a project team.
relatedMembranes
Project Team
relatedAssets
null
relatedProtocols
Project Protocol
criteria
Whatever means defined in the scope of work to select project participants.
responsibilities
Execute assigned tasks; communicate progress; uphold values.
benefits
Compensation via project funds; attribution for contributions.
roleAddress
[…]
Role
Contributor executing defined tasks within an approved project scope.
Benefits
Compensation via project funds; attribution for contributions; access to project tools and learning opportunities.
Rights
Access to needed information/tools for tasks; raise concerns/risks; request support or clarification; fair recognition of work.
Responsibilities
Complete assigned tasks with quality and timeliness; communicate status/risks; follow IP, publishing, and collaboration protocols; respect team agreements.

Project Lead

Metadata
id
RC-role-project-lead
name
Project Lead
description
Lead for a project within Regen Commons.
relatedMembranes
Project Team
relatedAssets
Commons Treasury Multi-Sig
relatedProtocols
Project Protocol, Treasury Management Protocol, Decision-Making Protocol
criteria
Capacity to execute approved scope; proposal accepted by Steward Council.
responsibilities
Deliver outcomes; manage allocated funds per milestones; coordinate contributors; report progress.
benefits
Funding per milestones; attribution for completed work; authority within approved scope.
roleAddress
[…]
Role
Scope lead responsible for delivering an approved project with defined milestones, budget, and self-governance plan.
Benefits
Milestone-based compensation; authority within approved scope; access to support and Resources; attribution for outcomes.
Rights
Request milestone fund releases; select/approve participants per scope; propose scope/budget adjustments; access necessary tools/data; fair review of performance.
Responsibilities
Deliver outcomes on time/within budget; coordinate Project Participants and communications; maintain records and publish reports/retrospectives; ensure protocol compliance (IP, publishing, treasury); surface and address conflicts per protocol.

Seed Member

Metadata
id
RC-role-seed-member
name
Seed Member
description
Founding participant automatically whitelisted to claim membership by virtue of participation in the formation process; same rights and responsibilities as a Member during MVP.
relatedMembranes
Community Assembly
relatedAssets
Constitution
relatedProtocols
Member Protocol, Decision-Making Protocol
criteria
Listed on the initial seed whitelist; alignment with Purpose and Values; acceptance of MVP protocols; claims role by accepting on-chain credential within the claim window.
responsibilities
Participate in governance; uphold values and protocols; peer accountability; vote on proposals; help bootstrap initial governance processes.
benefits
Voting rights; ability to propose projects; access to member-only resources; early recognition as founding participant; eligibility to vote in the initial steward election.
roleAddress
Hats role (Seed Member) (TBD)
isActive
true
Role
Founding Member of the Commons, recognized for participation in the formation process and granted the ability to claim membership with the same rights and responsibilities as a Member.
Benefits
All Member benefits (voting, proposals, member resources) plus early recognition and eligibility to vote in the initial Steward Council election.
Rights
Equal voting rights; seek advice or consent on proposals; access governance records; fair process in advancement and exit.
Responsibilities
Participate in discussions and votes; uphold Values and Protocols; peer accountability; support bootstrapping activities (e.g., Steward elections, initial processes) during MVP.

Steward

Metadata
id
RC-role-steward
name
Steward
description
Guardians of organizational identity and protocol integrity.
relatedMembranes
Steward Council
relatedAssets
Commons Treasury Multi-Sig, Constitution
relatedProtocols
Treasury Management Protocol, Decision-Making Protocol, Member Protocol, Conflict Protocol, Publishing Protocol
criteria
Selected via community election; meets eligibility defined by Member Protocol; term-limited.
responsibilities
Manage treasury per Treasury Management Protocols; publish decisions and reports and maintain documentation and auditability per Publishing Protocol; provide advice on proposals aligned with strategy per Decision Protocol; ensure integrity of organizational activities aligned with Identity.
benefits
Stewardship authority within defined scope; recognition.
roleAddress
Multisig signer (Gnosis Safe), Hats role (TBD)
appointment
Selected by seed members. Future: elected by members or via sortition
term
12 months with option for renewal
isActive
true
Role
Guardian(s) serving as authorized signers on the treasury multi-signature wallet (multisig) and executing governance operations within protocol-defined scope.
Benefits
Steward recognition; clear authority to execute actions within thresholds; access to context and support; reputation accrual.
Rights
Initiate/execute multi-sig financial transactions within Ops/Mid/Strategic tiers after decisions logged; request information for due diligence; convene votes, consent, or advice processes; pause disbursements if risk triggers per Treasury Management Protocol.
Responsibilities
Manage treasury per Treasury Management Protocols; publish decisions and reports and maintain documentation and auditability per Publishing Protocol; provide advice on proposals aligned with strategy per Decision Protocol; ensure integrity of organizational activities aligned with Identity.

Assets

This object defines an asset owned or managed by the network. Assets can be financial, digital, reputational, or intellectual property. Each asset is stewarded by one or more roles and governed by specific protocols.

Common Pool Resources

Metadata
id
RC-asset-resources
name
Common Pool Resources
description
A classification system for the diverse assets that compose the Regen Commons.
assetType
resources
relatedMembranes
members
relatedProtocols
resourcesProtocol (future)
relatedAssets
location
Add index location

Certification

Metadata
id
RC-resource-certification
name
Certification
description
Labels, protocols, and audits that legitimize Regen practices.
assetType
resource
relatedMembranes
relatedProtocols
relatedAssets
location
Add index location (for the type)
What
Labels, protocols, and audits that legitimize Regen practices.
  • This refers to the systems for impact verification and peer attestation, which can serve as a mechanism for determining levels of participation and governance weight.
Benefits
Legitimacy, recognition, market differentiation.
Internal Facility Needs
Standards setting, verification processes, registry systems.

Technology

What
Platforms, apps, and digital tools
  • This encompasses common-pooled technology licenses, apps, and open-source products that are shared for the benefit of members.
Benefits
Enable scaling, coordination, monitoring.
Internal Facility Needs
Shared infrastructure, APIs, open protocols, licensing systems.

Knowledge

What
Shared pool of practices, data, stories, and research.
  • This includes data pools, research, and bioregional organizing knowledge libraries that provide shared wisdom to the community.
Benefits
Collective intelligence, knowledge commons, innovation.
Internal Facility Needs
Data curation, versioning, attribution, community research support.

Branding

What
Visual identity, narrative, and other contributed brand assets..
  • This includes trademarks, logos, slogans, and domains, which form the core intellectual property of the commons.
Benefits
Legitimacy, cohesion, recognition, amplification.
Internal Facility Needs
Brand governance, brand use protocols, communication channels.

Facilities

What
Organizational, legal, and material backbone (funds, hosting, facilities).
Benefits
Stability, continuity, operational capacity.
Internal Facility Needs
Governance frameworks, financing protocols, coordination tools.

Constitution

Metadata
id
RC-asset-constitution
name
Constitution
description
The governing agreement of the Commons during MVP.
assetType
agreement
relatedMembranes
Community Assembly, Steward Council
relatedProtocols
Constitution Protocol
relatedAssets
null
location
Regen Commons MVP Constitution

Purpose: Define the MVP governance agreement, its Identity, Structure, and Protocols, serving as the source of legitimacy and clarity.

Location: Regen Commons MVP Constitution with change log entries per Constitution Protocol.

Related Membranes: Community Assembly (advice/consent), Steward Council (proposal and execution).

Related Protocols: Constitution Protocol (adoption and amendment), Publishing Protocol (public redlines and logs).

Governance & Permissions: Amendments use thresholds defined in the Decision-Making Protocol. Historical versions remain accessible to preserve institutional memory.

Operations & Usage: Reference identity and structure components via transclusions; keep links up to date as components evolve.

Transparency & Records: Publish proposals with redlines, rationales, and adoption records; retain prior versions.

Risks & Safeguards: Prevent unauthorized edits; require proper consent evidence; maintain consistent indexing and link integrity.

Governance Forum

Metadata
id
RC-asset-governance-forum
name
Governance Forum
description
Primary venue for proposals, records, and communications.
assetType
infrastructural
relatedMembranes
Community Assembly, Steward Council
relatedProtocols
Publishing Protocol, Decision-Making Protocol
relatedAssets
null
location
Forum/website (TBD)

Purpose: Provide a canonical venue for proposals, records, discussion, and publication, ensuring transparency and continuity.

Location: Forum/website (TBD) linked from official channels; access policy favors public readability.

Related Membranes: Community Assembly (discussion, advice), Steward Council (decisions and reports).

Related Protocols: Publishing Protocol (posting and record standards), Decision-Making Protocol (evidence of consent/votes).

Governance & Permissions: Clear posting templates; moderators ensure completeness and civility; records are immutable once decisions are executed, with edits tracked.

Operations & Usage: Host proposals, decisions, reports, retrospectives, and change logs; tag and index content for discoverability.

Transparency & Records: Link execution artifacts (transaction hashes, credential IDs) and maintain archives for audit.

Risks & Safeguards: Anti‑spam/capture moderation; backup and export routines; access levels for sensitive content as needed.

Commons Treasury

Metadata
id
RC-asset-treasury
name
Commons Treasury Multi-Sig
description
Primary treasury for MVP, controlled by Steward Council for allocations per protocol.
assetType
financial
relatedMembranes
Steward Council
relatedProtocols
Treasury Management Protocol, Decision-Making Protocol
relatedAssets
null
location
Gnosis Safe (address TBD)

Purpose: Primary treasury for MVP, enabling timely, legitimate funding of Commons operations and projects under clear, tiered rules.

Custody & Location: Gnosis Safe multi-sig (address TBD) with designated Stewards as signers per Treasury Management Protocol. Regen.eth ENS will likely be used as public facing address.

Related Membranes: Steward Council (execution and oversight).

Related Protocols: Treasury Management Protocol (tiers and approvals), Decision-Making Protocol (domain application and quadratic voting for mid‑tier).

Governance & Permissions: Stewards execute transactions within Ops/Mid/Strategic tiers after required off‑chain approvals (advice/consent/vote) and on‑chain enforcement (timelock where applicable). Role‑based authority is revocable via collective vote.

Operations & Usage: Funds are released by milestone verification for projects and for approved operational expenses. Thresholds define when discretion, vote, or consent is required. All requests and approvals reference forum records.

Transparency & Records: Publish allocations, approval evidence (votes/consent), transaction hashes, and periodic reports to the Governance Forum.

Risks & Safeguards: Timelocks for strategic disbursements; signer rotation at term end; conflict pathway for disputes; clear audit trail to reduce capture or misuse.

Brand Assets

Metadata
id
RC-asset-brand-assets
name
Brand Assets
description
Regen Commons identity assets including logos, domains, and narrative guidelines.
assetType
reputational
relatedMembranes
Community Assembly, Steward Council
relatedProtocols
Brand Usage Protocol
relatedAssets
null
location
regen.eth (domain/account), brand repository (TBD)

Purpose: Hold and steward the Regen Commons identity (logo assets and guides, web2 and web3 domains, narrative, email account) to protect legitimacy and enable aligned, shared use.

Location: brand repository (TBD); credentials managed per Brand Usage Protocol.

Related Membranes: Community Assembly (advice), Steward Council (certified approvals and enforcement).

Related Protocols: Brand Usage Protocol (fair‑use vs certified), Decision-Making Protocol (consent mechanisms), Conflict Transformation Protocol (dispute handling).

Governance & Permissions: Generic fair use is permissionless within published guidance and the Commons conditional license. Certified uses require steward‑led consent and are credentialed on‑chain. Misuse may lead to revocation subject to review and Conflict Protocol.

Operations & Usage: Publish and maintain brand guidelines; issue credentials; log terms and royalties where relevant; track usage narratives and outcomes.

Transparency & Records: Approvals, revocations, and guideline updates are published in the Governance Forum.

Risks & Safeguards: Periodic revision of guidance; appeals for certified decisions; documentation of cases for learning.

Core IP

Metadata
id
RC-asset-core-ip
name
Core IP
description
Foundational intellectual property and documentation stewarded by the Commons.
assetType
intellectual property
relatedMembranes
Community Assembly
relatedProtocols
IP Protocol, Publishing Protocol
relatedAssets
Constitution
location
Repositories and knowledge bases (TBD)

Purpose: Preserve, attribute, and share the Commons’ foundational knowledge and IP in ways that uphold integrity and enable reuse.

Location: Repositories and knowledge bases (TBD), with licensing captured in credentials per IP Protocol.

Related Membranes: Community Assembly (advice and peer review).

Related Protocols: IP Protocol (intake, peer review, non‑revocability upon acceptance), Publishing Protocol (public record).

Governance & Permissions: Submissions undergo advice + peer review; accepted contributions become non‑revocable commons records. Licenses/credentials specify terms; attribution is mandatory.

Operations & Usage: Curate submissions, maintain metadata quality, link to projects and learning artifacts; provide clear citation practices.

Transparency & Records: Publish acceptance decisions, licenses, and changelogs in the Governance Forum.

Risks & Safeguards: Avoid plagiarism/misattribution; consent and privacy for sensitive material; clear difference between draft (withdrawable) and accepted (non‑revocable) works.

Communication Channels

Metadata
id
RC-asset-comms
name
Communication Channels
description
The shared communication channels operated by Commons Stewards, including email lists, Telegram group, and any future communication platforms.
assetType
platform
relatedMembranes
Community Assembly, Steward Council
relatedProtocols
Moderation Protocol, Communication Protocol
relatedAssets
null
location
Regen Commons Email Lists, Regen Commons Telegram Group

Purpose: To enable effective communication, timely information sharing, and focused discussion for the governance and operation of the Regen Commons.

Location: A directory of official channels and access instructions is maintained and published by the Commons Stewards.

Related Membranes: Community Assembly (participation), Steward Council (administration and moderation).

Related Protocols: Moderation Protocol (defining conduct and enforcement), Communication Protocol (guiding official announcements and discussions).

Governance & Permissions: Access permissions and moderation roles are managed by Commons Stewards. The creation or retirement of an official channel requires a decision by the Steward Council.

Operations & Usage: Used for official announcements, governance proposals, community discussions, and coordinating activities. Stewards are responsible for channel administration and moderation.

Transparency & Records: Public-facing channels will have publicly accessible archives where feasible. Key decisions and moderation actions are logged internally by the Stewards.

Risks & Safeguards: Prevent spam and disruptive behavior through active moderation. Safeguard against unauthorized administrative access by limiting permissions to current Stewards. Ensure channel continuity through documented procedures for transferring ownership.

Membranes

Boundaries that regulate participation, permissions, and trust thresholds.

Steward Council

Metadata
id
RC-membrane-steward-council
name
Steward Council
description
Interim stewardship membrane composed of elected multisig stewards to manage treasury and MVP governance execution.
type
council
relatedProtocols
Decision-Making Protocol, Treasury Management Protocol, Member Protocol
relatedMembranes
Commons Members, Project Team
parentMembranes
Commons Members
childMembranes
null
relatedAssets
Commons Treasury Multi-Sig, Constitution
relatedRoles
Steward
sameAs
null
workSpaceLink
null
Decision Making
Simple majority voting and role-based authority on operational matters, and supporting advice and consent processes on key decisions per decision protocol.
Meeting Frequency
Bi-weekly for first 6 months, then monthly
Transparency
All decisions documented and shared with community
Oversight
Community review and feedback process for major decisions

Commons Member Assembly

Metadata
id
RC-membrane-commons-members
name
Commons Members
description
Composed of all recognized members of the commons.
type
assembly
relatedProtocols
Member Protocol, Decision-Making Protocol
relatedMembranes
Steward Council, Project Team
parentMembranes
null
childMembranes
Project Team
relatedAssets
Constitution
relatedRoles
Member
sameAs
null
workSpaceLink
null
Composition
All seed members, members, and stewards
Meetings
Monthly community calls for updates, input, and relationship building
Powers
Participation in major decisions (whether via advice, consent, role-based, or voting, depending on the decision type), steward selection, proposal development
Participation
Open discussion, consensual temperature checks, recommendation development

Project Teams

Metadata
id
RC-membrane-project-team
name
Project Team
description
Membrane for approved initiatives operating under a scoped self-governance plan and milestone-based funding.
type
project
relatedProtocols
Project Protocol, Treasury Management Protocol, Decision-Making Protocol
relatedMembranes
Commons Members, Steward Council
parentMembranes
Commons Members
childMembranes
null
relatedAssets
Commons Treasury Multi-Sig
relatedRoles
Project Lead, Project Participant
sameAs
null
workSpaceLink
null
Temporal State
Temporary
Composition
Project Participants listed in approved project plan or approved by Project Lead.
Meetings
As defined by project scope
Powers
Membrane-based authority (Project Team, or any Roles within) with accountability cycles. Any action within approved project scope that does not conflict with this constitution
Participation
As defined by project scope

Operations Teams

Metadata
id
RC-membrane-operations-team
name
Operations Team
description
Operational membrane responsible for core commons infrastructure, facilities, programs, and ongoing operational work streams.
type
operations
relatedProtocols
Operator Protocol, Treasury Management Protocol, Decision-Making Protocol
relatedMembranes
Community Assembly, Steward Council
parentMembranes
Community Assembly
childMembranes
null
relatedAssets
Commons Treasury Multi-Sig, Governance Forum
relatedRoles
Operator
sameAs
null
workSpaceLink
null
Temporal State
Ongoing
Composition
Operator Leads and Operator Team
Meetings
regular operational check-ins; infrastructure planning sessions; emergency response coordination
Powers
operational decision-making within infrastructure scope approved by Steward Council; resource allocation for operational needs; coordination of operational work streams
Participation
As defined by operation team protocol

Protocols

Cultural Protocols

Decision-Making Protocol

Metadata
id
RC-protocol-decision-making
name
Decision-Making Protocol
description
Tiered decision-making processes (consent, advice, role-based, temp check) applied by domain with on-chain execution.
initializationEvent
MVP activation; roles credentialed; forum open.
associatedFunctions
sense-making, decision making, coordination, resource allocation, culture
associatedRoles
Member, Steward (Multisig), Project Lead
relatedMembranes
Community Assembly, Steward Council, Project

Purpose: Provide clear, lightweight pathways for how decisions are made across membranes, balancing human discernment with on‑chain enforcement.

Initialization: This protocol activates at MVP launch when roles are credentialed and the Governance Forum is open for proposals, records, and votes.

Participants: Members participate in advice/consent and voting; Stewards (multi-sig) execute approved actions on‑chain and manage treasury protocols; Project Leads coordinate project‑level execution.

Decision Domains & Flows
Membership Decisions

Foundation Period (Months 0-6) — Lower Barrier Entry:

  1. Invitation: Seed Members exercise individual authority to extend invitations (up to five per member) to prospective members demonstrating alignment with Purpose and Values
  2. Onboarding: Prospective members complete structured enculturation sequence of two to three (2-3) ritualized onboarding events facilitated by Gardeners and Stewards
  3. Lazy Consent Review: Upon completion of onboarding, prospective members enter seven (7) day lazy consent window
    • Any existing Member may raise substantive objections
    • Objections trigger formalized consent vote within Community Assembly
    • Absence of blocking objections results in automatic advancement
    • Batched processing permitted for operational efficiency
  4. Credential Claim: Successful candidates receive eligibility to claim non-transferable membership credential, constituting formal consent to Constitution and election to sortition pool
  5. Registry Update: EAS registry reflects new member status and governance eligibility

Transition Period (Month 6+) — Higher Barrier Entry: Following Foundation Period, upon Steward Council determination of adequate cultural coherence and governance capacity, membership admission transitions to enhanced verification model (specific mechanisms to be collaboratively defined during Foundation Period, potentially including attestation systems or Operations Team review).

Role Advancement: Advancement to higher‑responsibility roles (e.g. project lead, operator, gardener) requires advice process followed by consent at the appropriate membrane. Steward selection follows protocols defined in Steward Protocol, transitioning to sortition-based selection concurrent with membership barrier elevation.

Licensee Engagement

Generic Fair Use: Permissionless within published guidance and Commons conditional use license framework.

Certified Use: Steward-led consent process required for certified or narrow uses. Approved parties receive non-transferable access credential/NFT. Terms, duties, and royalty obligations are recorded in Governance Forum.

Intellectual Property Contribution

Submission: Contributors submit works with attribution and licensing intent to Governance Forum.

Review: Advice and peer review process conducted by community members and Gardeners.

Acceptance: Upon community acceptance, contributions become non-revocable commons resources with clear attribution, credentialed and licensed per IP Protocol.

Operational Decisions

Core Operations: Routine operational activities (credential issuance, infrastructure maintenance, software updates) are executed via delegated role-based authority with defined accountability cycles. Such delegations remain revocable via collective vote, with timelock enforcement where applicable.

Member Exit

Voluntary Departure: Members may exit voluntarily at any time. Upon exit, credentials are revoked and registry updated accordingly.

Inactive Member Review: Community conducts periodic review (every twelve months) to maintain registry accuracy. Inactive members may be removed following due process.

Non-Revocable Contributions: Accepted IP contributions and commons resources remain non-revocable regardless of member status.

Brand Resource Governance

Fair-Use Guidance: Stewards facilitate ongoing development and refinement of fair-use guidance, ensuring coherence between software licenses and brand licenses. Adoption of conditional use license framework for all IP associated with "Regen" designation.

Permissionless Use: Anyone may adopt Regen use patterns compliant with published fair-use guidelines. All members share responsibility for monitoring usage patterns and maintaining legitimacy.

Certified Use: Certified uses require formal consent process as outlined in Brand Usage Protocol.

Enforcement: Misuse follows Conflict & Tension Protocol escalation pathway. Persistent misuse may result in on-chain credential revocation.

Financial Decisions (Tiered Governance)

Operational Tier: Expenditures below defined financial and temporal thresholds (subject to twelve-month re-evaluation) are executed via role-based discretion (e.g., Treasurer Hat). Stewards execute directly via multi-signature authorization.

Project Tier: Project funding requests follow advice process, followed by quadratic voting among credentialed members. Successful votes authorize multi-signature execution per Treasury Management Protocol.

Strategic Tier: Major allocations require collective consent from Commons Member Assembly or Steward Council. Approved transactions execute via on-chain timelock (one to three day delay) to enable community review and emergency intervention if necessary.

Strategic Planning

Priority Setting: Annual strategic priorities established through collective sense-making processes within Community Assembly.

Action Alignment: Strategic initiatives require advice and consent processes to ensure collective alignment.

Automation: Only low-risk, routinized activities are candidates for on-chain automation.

Conflict Resolution

Escalation Pathway: Conflicts follow graduated resolution process: direct dialogue → facilitated mediation → binding arbitration.

Enforcement: Outcomes (including credential revocation, fund reallocation, or other remedies) are enforceable on-chain and recorded in Governance Forum.

Protocol Reference: See Conflict & Tension Protocol for detailed procedures and requirements.

Records & Transparency: Each decision should link to Governance Forum context, evidence of consent/votes, and, when relevant, transaction hashes or credential IDs. All meeting minutes are made available to members. Changelogs are maintained for Protocols and the Constitution.

Safeguards: Clear thresholds, timelocks for high‑stakes moves, revocability of delegated authority, and an active conflict protocol protect against capture and support legitimacy.

Process Flows Summary:

Membership (Foundation Period): Invitation → Onboarding Events (2-3) → Lazy Consent Review (7 days) → Credential Claim → Registry Update

Membership (Post-Foundation): Application → Enhanced Verification → Community Review → Approval → Onboarding → Credential Claim

Stewardship (Foundation Period): Nomination → Election by Seed Members → Term Confirmation → Ongoing Service

Stewardship (Post-Foundation): Nomination → Community Advice → Sortition Selection → Term Service

General Operations: Proposal → [Advice/Consent/Vote per Domain] → Execution → Documentation → Review

Conflict & Tension Protocol

Metadata
id
RC-protocol-conflict
name
Conflict & Tension Protocol
description
Graduated pathway from reflection to dialogue, mediation, and arbitration, with repair and learning.
initializationEvent
MVP activation; mediator pool identified; arbitration guardrail defined.
associatedFunctions
culture, coordination, decision making, learning
associatedRoles
Member, Steward (Multisig)
relatedMembranes
Community Assembly, Steward Council

Purpose: Normalize conflict as a signal, provide a humane path to address tensions, and protect the commons’ integrity.

Initialization: a mediator team is identified and the arbitration guardrail is defined; members are oriented to the protocol during onboarding; a tension or conflict is worked out between members (and if additional support needed, mediation or arbitration is made available).

Participants: Any member may initiate; mediators and, if necessary, arbitrators support the process; Stewards enforce outcomes on‑chain where required.

Pathway: Conflicts begin with self‑reflection and direct dialogue. If dialogue stalls or is unsafe, a Gardener or external mediator facilitates supported dialogue. If still unresolved, external arbitration serves as a last resort, weighing mission, values, and community health. Outcomes may include credential burns or fund reallocations and must be documented. If infractions are resolved, but continue to repeat, member is removed after 3 repeat infractions.

Repair & Learning: After resolution, parties reflect on harms and repairs, share lessons at the appropriate scope, and propose updates to norms if patterns persist. Training and periodic circles build community capacity over time.

Steps: Self-Reflection: clarify experiences, needs, and desired outcomes before engagement; Direct Dialogue: share impacts/needs, use "I" statements, ask with curiosity, make specific requests; Mediation: invite neutral mediator if dialogue stalls/unsafe; support co-created agreements; Arbitration (Last Resort): trusted pool issues binding decision guided by mission/values and community health; Enforcement: outcomes can trigger credential burn or fund reallocation on-chain per protocols; Repair & Learning: reflect on harms/reparations; share learnings; update norms if patterns emerge; Capacity Building: train in listening, mediation; normalize tension processing rituals

Role Protocols

Member Protocol

Metadata
id
RC-protocol-member
name
Member Protocol
description
Admission, advancement, and exit of members; credentialing and registry updates.
initializationEvent
Adoption of MVP constitution and initial member whitelist.
associatedFunctions
sense-making, decision making, coordination, culture
associatedRoles
Member
relatedMembranes
Community Assembly

Purpose: This protocol governs how people become members, advance to deeper stewardship, and exit, while keeping records consistent on-chain. It establishes a phased approach to membership admission designed to ensure cultural coherence, collective trust, and operational readiness for distributed governance.

Initialization: The protocol becomes active upon adoption of the MVP Constitution and the publication of an initial whitelist of seed members.

Requirements: Alignment with Purpose and Values; demonstrated contribution and engagement; acceptance of Constitution and Protocols; completion of onboarding sequence and credential claim; willingness to participate in governance; maintenance of good standing. For project team participation, relevant skills and availability are required.

Participants: Seed Members initiate invitations; Gardeners and Stewards facilitate enculturation; Community Assembly exercises consent authority; prospective members complete onboarding requirements.

Membership Phases
Phase 1: Foundation Period (Months 0-6)

Lower Barrier Entry Process — Designed to establish a foundational membership cohort of approximately 100 individuals while maintaining cultural integrity and collective alignment.

Invitation Authority: Each Seed Member may extend invitations to up to five (5) individuals who demonstrate alignment with organizational Purpose and Values and show contributory capacity.

Onboarding Sequence: Prospective members must complete a structured enculturation process consisting of:

  1. Participation in two to three (2-3) ritualized onboarding events conducted over the Foundation Period
  2. Engagement with constitutional frameworks, decision-making protocols, and conflict transformation practices
  3. Integration into cultural norms and collective sense-making processes

Lazy Consent Review: Following completion of the onboarding sequence, each prospective member enters a seven (7) day lazy consent window during which:

  • Any existing Member may raise substantive objections based on alignment with Purpose, Values, or Protocols
  • Objections trigger a formalized consent process within the Community Assembly
  • Absence of blocking objections results in automatic advancement to credential claim eligibility
  • Batched processing of admissions may be employed for operational efficiency

Credential Issuance: Upon successful completion of the lazy consent period, prospective members receive eligibility to claim a non-transferable membership credential. Credential acceptance constitutes formal consent to this Constitution and includes election to join the sortition pool for future governance selection processes.

Registry Update: The EAS registry is updated to reflect new member status, participation history, and governance eligibility.

Phase 2: Transition Period (Month 6+)

Barrier Adjustment: Following the Foundation Period and upon determination by the Steward Council that sufficient cultural coherence and governance capacity have been established, membership criteria transition to a higher-threshold model:

Higher Barrier Entry Process — Designed to ensure sustained organizational integrity through enhanced verification mechanisms (specific model to be determined collaboratively during Foundation Period, potentially including attestation systems, Operations Team review, or other community-defined mechanisms).

Governance Democratization: Concurrent with membership barrier elevation, stewardship selection transitions to sortition-based processes, lowering barriers to governance participation while ensuring distributed authority.

Legacy Provisions
Seed Members
Automatically whitelisted from formation participants; claim role by accepting non-transferable credential within published claim window; EAS registry updated accordingly. Unclaimed credentials revert to standard admission pathways. Seed Member designation sunsets after twelve (12) months, transitioning to standard Member status.
Project Team Participation
Selection by Project Lead or via process defined in project scope; requires agreement to project-specific terms, timelines, and deliverables.

Advancement: Moving into roles uses an advice process to signal nomination + consent process at the relevant membrane level that the role contributes to, and is informed by transparent participation thresholds recorded in the registry.

Exit and List Hygiene: Members may depart voluntarily or via initiated exit. The community periodically reviews inactivity to keep the registry accurate. On exit, membership credentials are burned and the registry is updated. Access to assets is adjusted per protocols. Accepted IP contributions remain non‑revocable and part of the Common Pool Resources.

Key Responsibilities During Foundation Period

Seed Members: Exercise strategic discernment in cohort composition, extending invitations to individuals who demonstrate both alignment and contributory capacity. Responsible for cultivating a diverse yet coherent foundational membership body.

Gardeners and Stewards: Design and facilitate enculturation processes, onboarding sequences, and ritualized events. Ensure prospective members develop functional literacy in constitutional frameworks, decision-making protocols, and cultural practices. Prepare governance infrastructure and mechanisms to support transition to sortition-based selection in Phase 2.

Community Assembly: Exercise consent authority through lazy consent review processes. Maintain collective accountability for membership composition and cultural coherence.

Dependencies and Preparatory Work

Business Model Development: Establishment of clear membership benefits and value propositions (targeted for completion within initial months of Foundation Period) to inform invitation processes and support sustainable organizational operations.

Participatory Design: Engagement in collaborative business model design processes serves dual purposes: defining membership value propositions and identifying prospective members aligned with organizational direction.

Steps: Invitation → Onboarding Sequence (2-3 Events) → Lazy Consent Review (7 Days) → Credential Claim Eligibility → Registry Update → [Ongoing] Advancement or Exit

Steward Protocol

Metadata
id
RC-protocol-steward
name
Steward Protocol
description
This protocol outlines the process for adding and removing a Steward.
initializationEvent
Change in role state proposed.
associatedFunctions
decision making, resource allocation, coordination
associatedRoles
Steward, Seed Member, Member
relatedMembranes
Steward Council, Community Assembly

Purpose: Establish legitimate stewardship selection through initial democratic election, then transition to sortition-based selection to prevent power concentration while ensuring competency.

Initialization: Change in role state proposed.

Requirements: Active Member in good standing; availability for meetings and transaction signing when necessary; demonstrable trust and process/treasury competency; commitment to transparency and Conflict Protocol.

Participants: Seed Members conduct initial election; Community Assembly provides nominations and advice; eligible Members may be nominated or self-nominate; selected Stewards receive credentials and permissions.

Selection:

Initial Election
Seed Members vote to elect the first Steward Council (5-7 members) for a 9-month term (e.g., via Snapshot or equivalent). This establishes initial legitimacy and accountability during the critical MVP phase.
Subsequent Selection
After the initial term, a peer nomination process opens where eligible members may be nominated or self-nominate. The community provides advice on nominations and selection criteria.
Future Intention - Sortition Process
Random selection from the nominated pool uses weighted criteria including participation history, trust signals from the registry, and relevant expertise. This prevents popularity contests while ensuring competency.

Role Assignment: Selected stewards receive multi-sig permissions (Gnosis Safe signer access) and Hats credentials with appropriate scope and authority for treasury management and governance execution.

Removal and Term Management: Stewards serve 9-month terms with staggered rotation to ensure continuity unless an election is called by 2/3 vote of Members before the 9 month term is complete. Regular accountability cycles and performance reviews conducted by the Project Evaluation Team to maintain quality and legitimacy. Stewards are removed after a 9-month term or after an election has been called to remove them.

Transition: Outgoing stewards transfer knowledge, context, and permissions to incoming cohort through structured handoff processes, ensuring smooth governance continuity.

Steps (MVP): Nomination Period → Candidate Statements → Election → Confirmation → Exit

Project Lead Protocol

Metadata
id
RC-protocol-project-lead
name
Project Lead Protocol
description
How to become a Project Lead through scoped proposal submission and approval.
initializationEvent
Commons opens project intake process.
associatedFunctions
decision making, resource allocation, coordination, learning
associatedRoles
Project Lead, Steward
relatedMembranes
Project, Steward Council, Community Assembly

Purpose: Define how individuals become Project Leads through proposal submission and approval, ensuring clear scope, accountability, and learning.

Initialization: The protocol activates when the Commons announces project intake and opens the Governance Forum for proposals.

Requirements: Demonstrated capacity and relevant expertise; clear scope, milestones, budget, and reporting plan; alignment with strategy and Protocols; availability to coordinate Project Participants.

Participants: Prospective Project Leads submit proposals; the Community Assembly provides advice; project review team reviews and approves; Project Participants are engaged by the Lead.

Selection: Proposal submitted to Governance Forum; advice process; project review team approval; role credentialed (Hats) with authorized scope and milestones.

Proposal & Review: Submit a detailed proposal including scope, milestones, self-governance plan, budget, and timeline. The community offers advice during a review period; proposers address feedback and iterate. The project review team evaluates for strategic alignment and protocol compliance.

Role Assignment: Upon approval, the Project Lead receives a credentialed role (Hats) with authorized scope and milestones. The role is scoped to the specific project and expires upon completion.

Execution & Accountability: Project Leads execute within approved parameters, coordinate Participants, manage milestone-based funding, and report progress and variances to the Governance Forum.

Closeout: Upon completion, Project Leads deliver outcomes, publish retrospectives, and the role expires with the project. Learnings are captured for future reference.

Steps: Nomination → Vetting → Approval → Assignment → Onboarding → Active → Membership Review → Removed

Licensed Partner Protocol

Metadata
id
RC-protocol-licensed-partner
name
Licensed Partner Protocol
description
How organizations gain, maintain, and lose Licensed Partner status through brand usage agreements.
initializationEvent
Brand assets committed to Commons custody; fair-use guidance published.
associatedFunctions
culture, decision making, coordination
associatedRoles
Licensed Partner, Steward (Multisig)
relatedMembranes
Community Assembly, Steward Council

Purpose: Define the lifecycle of Licensed Partner status, from application through credentialing, use, and potential expiration.

Initialization: The protocol activates when brand assets are committed to Commons custody and fair-use guidance is published, enabling the Licensed Partner application process.

Requirements: Demonstrated alignment with Values; commitment to brand guidelines; acceptance of license terms and reporting expectations; no prior misuse.

Participants: Organizations seeking Licensed Partner status; Stewards review applications and manage credentials; Community Assembly provides advice on criteria and recognition.

Selection: Apply via Brand Usage Protocol; values alignment assessment; steward-led consent; issuance of a non-transferable access credential; license terms (including any fees/royalties) recorded.

Application Process: Organizations submit applications with values alignment assessments and proposed use cases. The process follows the Brand Usage Protocol for review and consent.

Credentialing: Upon approval, organizations receive non-transferable brand access credentials that grant Licensed Partner status and access to partner resources and recognition systems.

Role Activation: Licensed Partners gain community recognition, and the ability to use Regen branding within their approved scope and terms.

Ongoing Use: Licensed Partners must adhere to brand guidelines, contribute back per agreed terms (fees, stories, attribution), and maintain legitimacy through consistent alignment with commons values.

Monitoring & Compliance: Regular compliance checks ensure adherence to terms. Disputes are resolved through the Conflict Transformation Protocol, with escalation paths for persistent issues.

Expiration: Licensed Partner status expires if misuse persists after the conflict pathway is exhausted. Credentials are revoked and access is terminated, with the decision recorded in the Governance Forum.

Steps: Application → Review → Credentialing → Role Activation → Ongoing Use → Monitoring → Expiration

Gardener Protocol

Metadata
id
RC-protocol-gardener
name
Gardener Protocol
description
How to become a Gardener through specialized training and demonstrated caretaking skills.
initializationEvent
Training programs established; Gardener role criteria defined.
associatedFunctions
learning, coordination, culture
associatedRoles
Gardener, Member
relatedMembranes
Community Assembly, Project

Purpose: Develop and credential community members with specialized skills for tending, curating, and caring for commons resources and relationships.

Initialization: The protocol activates when training programs are established and Gardener role criteria are defined by the community.

Requirements: Alignment with Purpose/Values; demonstrated curation/care skills (knowledge organization, facilitation, documentation); consistent participation; commitment to publishing and conflict transformation practices.

Selection: Nominated or self‑nominated; advice + consent at the membrane level (e.g., Community Assembly for network‑wide gardening, or within a Project for project‑scoped gardening). Role credentialed via Hats with a defined scope/term where applicable.

Participants: Members seeking Gardener roles; training facilitators; Community Assembly provides advice and consent; Projects may have scoped Gardener roles.

Training & Skills: Complete specialized training in relevant stewardship areas such as relational tending, conflict mediation, knowledge gardening, and grant program operations. Demonstrate caretaking skills through community participation and meaningful contributions.

Role Assignment: Nomination or self-nomination triggers an advice + consent process at the appropriate membrane level (Community Assembly for network-wide gardening, or within Projects for scoped roles). Upon approval, the role is credentialed (Hats) with defined scope and term where applicable.

Execution & Responsibilities: Gardeners execute caretaking responsibilities within their authorized scope, including curating resources, maintaining documentation, supporting community rituals, monitoring health/abundance metrics, and facilitating learning loops.

Review & Renewal: Periodic review ensures Gardeners maintain performance standards and meet evolving community needs. Roles may be renewed, adjusted, or transitioned based on community feedback and changing requirements.

Steps: Training → Demonstration → Nomination → Credentialing → Role Execution → Review & Renewal

Operator Protocol

Metadata
id
RC-protocol-operator
name
Operator Protocol
description
How to become an Operator through application, assessment, and approval for ongoing operational work streams.
initializationEvent
Operations Team established; operational infrastructure needs identified.
associatedFunctions
coordination, resource allocation, learning
associatedRoles
Operator, Member
relatedMembranes
Operations Team, Community Assembly

Purpose: Define how individuals become Operators through application, assessment, and approval for ongoing operational work streams related to commons infrastructure, facilities, and programs.

Initialization: The protocol activates when the Operations Team is established and operational infrastructure needs are identified, enabling the Operator application process.

Participants: Prospective Operators submit applications; Steward Council evaluates and approves; Operations Team provides operational guidance and oversight.

Application Process: Individuals submit applications with operational skills assessments and proposed scope of work. Applications should demonstrate relevant experience in infrastructure management, facilities operations, or program coordination.

Assessment & Approval: The Steward Council evaluates applications based on demonstrated operational skills, capacity for ongoing work, and alignment with identified infrastructure needs. Approval is based on demonstrated capabilities and current operational requirements.

Role Assignment: Upon approval, Operators receive Hats credentials with defined operational scope and responsibilities. The role is scoped to specific operational work streams and infrastructure areas.

Execution & Monitoring: Operators perform operational work streams within their approved scope, maintaining infrastructure and facilities. Regular performance reviews, infrastructure status reporting, and operational metrics tracking ensure quality and accountability.

Renewal & Continuity: Periodic review and renewal processes ensure Operators maintain performance standards and meet evolving infrastructure needs. Roles may be adjusted, expanded, or transitioned based on operational requirements and community feedback.

Steps: Application → Assessment → Approval → Role Assignment → Execution → Monitoring → Renewal

Asset Protocols

Brand Usage Protocol

Metadata
id
RC-protocol-brand
name
Brand Usage Protocol
description
Access, fair-use guidance, certified use approvals, and revocation processes protecting brand integrity.
initializationEvent
Brand assets committed to Commons custody.
associatedFunctions
culture, decision making, coordination
associatedRoles
Licensed Partner, Steward (Multisig)
relatedMembranes
Steward Council, Community Assembly

Purpose: Protect Regen Commons brand integrity while enabling legitimate, commons‑aligned use.

Initialization: The protocol becomes active when Regen Commons brand assets are utilized.

Participants: Licensed Partners and Members engage the brand; Stewards oversee guidance, approvals, and enforcement.

Generic Fair Use: Anyone may use the Regen Commons brand within the published fair‑use guidance and the Commons conditional use license, without a bespoke approval. Community members help observe and uphold the guidance.

Monitoring & Enforcement: Misuse triggers the conflict pathway first (dialogue and mediation). If unresolved, stewards may revoke membership on‑chain. Stewards periodically update guidance and criteria with community input.

Steps: Generic Fair Use (permissionless): anyone may adopt Regen use patterns that comply with published fair-use guidelines and the Commons conditional use license; Certified Regen (consented): steward-led consent process for certified/narrow uses; values alignment assessment; appeals available; Credentialing: issue non-transferable brand access credential; record terms; royalties logged where relevant; Monitoring & Enforcement: transparent oversight; conflict pathway first; revoke credential if misuse persists; Governance: stewards support cyclical revisions to fair-use guidance and certified criteria; members may propose changes

Constitution Protocol

Metadata
id
RC-protocol-constitution
name
Constitution Protocol
description
Adoption, amendment, and publication process for the Constitution.
initializationEvent
MVP Constitution proposed for adoption by Steward Council.
associatedFunctions
decision making, culture, learning
associatedRoles
Member, Steward (Multisig)
relatedMembranes
Community Assembly, Steward Council

Purpose: Provide a clear and participatory path for adopting and amending the Constitution.

Initialization: The MVP Constitution is proposed by the interim Steward Council (current Coordination team) for adoption, after which any amendments use this protocol.

Participants: Members and Stewards co‑steward constitutional changes; the Community Assembly provides input on proposed decisions to determine if safe enough for adoption via advice process, or requires consent.

Continuity: Historical versions remain accessible, preserving institutional memory and legitimacy.

Steps/ Change Flow: A proposal presents redlines and rationale. An advice window gathers feedback; authors iterate. Consent thresholds follow the Decision‑Making Protocol (e.g., assembly consent for major changes). Upon approval, redlines are merged, Constitution links are updated, and a change log entry is published.

IP Protocol

Metadata
id
RC-protocol-ip
name
IP Protocol
description
Intake, peer review, attribution, licensing, and protection for contributed IP and knowledge.
initializationEvent
Governance Forum open for submissions; legal framework initialized.
associatedFunctions
learning, coordination, culture
associatedRoles
Member, Project Lead, Steward (Multisig)
relatedMembranes
Community Assembly

Purpose: Provide a clear path to share knowledge and IP into the commons with proper review, attribution, and protection.

Initialization: The Governance Forum is open for submissions and the legal framework for conditional use is in place.

Participants: Members submit works; contributors and gardeners support peer review; Stewards ensure records and alignment.

Submission & Review: Authors submit works with attribution and licensing intent, agreeing to the Commons conditional use license. The community conducts an advice + peer review process and records the acceptance decision.

Acceptance & Record: Upon acceptance, contributions become non‑revocable commons records. Licenses/credentials are issued and works are published with clear attribution.

Access Changes: Authors may request access changes for unaccepted submissions. Accepted works remain in the commons record for continuity and legitimacy.

Steps: Submit IP/knowledge with attribution and licensing intent; agree to Commons conditional use license; Peer review/advice (contributors/gardeners); document acceptance decision; Once accepted: contribution is non-revocable; record license/credential; publish to repository with attribution; Access withdrawal: contributors may request access changes to unaccepted submissions; accepted works remain in commons record

Publishing Protocol

Metadata
id
RC-protocol-publishing
name
Publishing Protocol
description
Public documentation of proposals, decisions, and learnings for legitimacy and transparency.
initializationEvent
Governance Forum activated; roles onboarded.
associatedFunctions
culture, learning, coordination
associatedRoles
Member, Project Lead, Steward (Multisig)
relatedMembranes
Community Assembly, Steward Council

Purpose: Ensure proposals, decisions, project learnings, and constitutional changes are visible and traceable.

Initialization: The Governance Forum is activated and roles are onboarded to publishing responsibilities.

Participants: Members and Project Leads publish; Stewards ensure completeness and continuity of records.

Legitimacy & Access: Publishing supports transparency and legitimacy. Public read‑access is preferred; sensitive details are redacted per policy where necessary.

Steps/ Publishing Flow: Proposals are posted with context, scope, and requested actions. Decisions are recorded with rationale, evidence of consent/vote, and execution links. Project reports and retrospectives are archived and tagged for discovery. Constitutional and protocol changes are logged with diffs and dates.

Treasury Management Protocol

Metadata
id
RC-protocol-treasury
name
Treasury Management Protocol
description
Tiered financial decision-making and execution for the Commons treasury.
initializationEvent
Treasury multi-sig configured; stewards elected.
associatedFunctions
resource allocation, coordination, decision making
associatedRoles
Steward (Multisig), Project Lead
relatedMembranes
Steward Council, Project

Purpose: This protocol establishes clear, tiered pathways for making and executing financial decisions from the Commons treasury.

Initialization: The protocol activates when the treasury multisig is configured and stewards are credentialed.

Participants: Stewards lead treasury execution; Project Leads request releases after milestone verification; members participate in mid‑ and high‑tier approvals.

Tiers & Approvals: Operational expenditures under a defined threshold are handled through delegated role‑based discretion. Mid‑tier allocations use an advice process followed by a quadratic vote by credentialed members; approved votes authorize the multisig to execute. Strategic allocations require collective consent (assembly/council) and execute via on‑chain timelock.

Transparency & Records: All allocations, votes, and transactions are published with sufficient detail to enable auditability and community oversight.

Steps: Ops Tier (< threshold): role-based discretion (e.g., Treasurer Hat); direct multisig execution; Project-Tier: advice + quadratic vote by credentialed members; multisig executes approved tx; Strategic Tier: collective consent (assembly/council) for major allocations; timelocked execution; Transparency: publish allocations and reports; maintain on-chain records.

Membrane Protocols

Steward Council Protocol

Metadata
id
RC-protocol-steward council
name
Steward Council Protocol
description
Lifecycle for Council decision-making, including proposal, approval, execution, and transparent reporting.
initializationEvent
Council convenes with elected/appointed Stewards and decision-making protocol in force.
associatedFunctions
decision making, role-based authority, oversight, resource allocation, transparency
associatedRoles
Steward, Operator, Commons Member (advice giver)
relatedMembranes
Steward Council, Commons Members Assembly, Operations Team

Purpose: Establish legitimate stewardship selection through phased governance approach: initial elected Steward Council during Foundation Period to ensure organizational stability and cultural coherence, transitioning to sortition-based selection to prevent power concentration while ensuring competency and distributed authority.

Initialization: Change in role state proposed, either through nomination period or electoral process as appropriate to current governance phase.

Requirements: Active Member in good standing; availability for meetings and transaction signing when necessary; demonstrable trust and process/treasury competency; commitment to transparency and Conflict Protocol; capacity to facilitate governance infrastructure development and member enculturation.

Participants: Seed Members conduct Foundation Period election; Community Assembly provides nominations and advice in subsequent phases; eligible Members may be nominated or self-nominate; selected Stewards receive credentials and permissions.

Selection Phases
Phase 1: Foundation Period (Months 0-6, Minimum)

Higher Barrier Steward Selection — Designed to ensure organizational stability, treasury security, and governance capacity development during critical formation phase.

Initial Election: Seed Members nominate and elect Interim Steward Council (five to seven members) for minimum six-month term via democratic voting mechanism (e.g., Snapshot or equivalent platform). This establishes initial legitimacy and accountability while foundational membership cohort is being established.

Term Duration: Interim Steward Council serves minimum six-month term, extendable by Seed Member determination until such time as:

  1. Foundation Period objectives are substantially achieved
  2. Membership cohort demonstrates adequate cultural coherence and governance literacy
  3. Infrastructure for sortition-based selection is operationally ready

Foundation Period Responsibilities: Interim Steward Council bears enhanced responsibility for:

  • Designing and supporting member enculturation processes and ritualized onboarding events
  • Developing governance agreements and decision-making infrastructure
  • Preparing sortition mechanisms and selection criteria
  • Ensuring foundational members develop functional literacy in constitutional frameworks
  • Stewarding treasury with heightened accountability during formation phase
  • Facilitating participatory business model development
Phase 2: Transition to Distributed Governance (Month 6+)

Lower Barrier Steward Selection — Concurrent with elevation of membership admission barriers, stewardship selection barriers are lowered to democratize governance participation.

Nomination Process: Following Foundation Period, peer nomination process opens where eligible Members may be nominated or self-nominate based on demonstrated participation, competency signals, and alignment with Purpose and Values.

Community Advice: Community Assembly provides advice on nominations, selection criteria, and governance needs during open advice period.

Sortition-Based Selection: Random selection from nominated pool employs weighted criteria including:

  • Participation history and contribution patterns recorded in registry
  • Trust signals and peer attestations
  • Relevant expertise and demonstrated competencies
  • Commitment to term obligations

This approach prevents popularity contests and power consolidation while ensuring distributed authority and ongoing competency.

Role Assignment: Selected Stewards receive multi-signature permissions (Gnosis Safe signer access) and Hats credentials with appropriate scope and authority for treasury management and governance execution.

Term Management: Post-Foundation Period Stewards serve defined terms (typically nine months) with staggered rotation to ensure continuity. Terms may be renewed through sortition process. Early removal requires two-thirds (2/3) vote of Members. Regular accountability cycles maintain quality and legitimacy.

Transition Protocol: Outgoing Stewards transfer knowledge, context, and permissions to incoming cohort through structured handoff processes, ensuring smooth governance continuity and institutional memory preservation.

Steps:

Foundation Period: Nomination → Candidate Statements → Election by Seed Members → Term Confirmation → Role Assignment → [Ongoing Service] → Transition or Extension Determination

Post-Foundation: Nomination Period → Community Advice → Sortition Selection → Credential Issuance → Term Service → Renewal or Transition

Commons Member Assembly Protocol

Metadata
id
RC-protocol-commons-assembly
name
Commons Members Assembly Protocol
description
Lifecycle for Assembly engagement, including proposal development, advice processes, and relationship building.
initializationEvent
Monthly Assembly call announced and agenda published in Governance Forum.
associatedFunctions
input gathering, proposal development, consent/voting, steward selection, relationship building
associatedRoles
Member, Seed Member, Steward, Facilitator
relatedMembranes
Commons Members Assembly, Steward Council, Project

Purpose: This protocol defines how the Assembly convenes members, participates in governance, and serves as the primary forum for collective input, relationship building, and legitimacy.

Initialization: Monthly community calls are announced and facilitated by Stewards or delegated facilitators. Agenda includes updates, input gathering, and proposals.

Participants: Seed Members, Members, and Stewards (all credentialed Commons members).

Proposal & Approval: Any member can bring forward a proposal or recommendation. Proposals are shared in advance in the Governance Forum. Temperature checks and consensus-building guide refinement. Final approvals depend on decision type per Decision Protocol: advice, consent, role-based authority, or voting.

Execution & Funding: Once approved, execution follows the appropriate operational or project protocol. Members may join as contributors; funding follows the Treasury Management Protocol.

Reporting & Closeout: Updates are shared in subsequent Assembly calls. Reports and learnings are archived in the Governance Forum for transparency and iteration.

Steps: Idea → Discussion → Temperature Check → Proposal Drafted → Community Input → Steward Council Consideration / Consent / Assembly Vote → Approved / Declined.

Project Team Protocol

Metadata
id
RC-protocol-project
name
Project Protocol
description
Lifecycle for scoped initiatives, including proposal, approval, execution, and reporting.
initializationEvent
Commons opens project intake process.
associatedFunctions
decision making, resource allocation, coordination, learning
associatedRoles
Project Lead, Project Participant, Steward
relatedMembranes
Project, Steward Council, Community Assembly

Purpose: This protocol defines how scoped initiatives are proposed, approved, executed, and closed, ensuring clarity, accountability, and learning.

Initialization: The Steward Council announces project intake aligned to strategic priorities and opens the Governance Forum to receive proposals.

Participants: Project Leads, Project Participants, and Stewards execute this protocol; the Community Assembly contributes advice and context.

Proposal & Approval: A Project Lead submits a proposal outlining scope, milestones, governance plan, and budget. The community offers advice; projects with funding associated follow the Treasury Management Protocol. Approved projects are credentialed, and milestones are recorded for tracking.

Execution & Funding: Funds are released by milestones via the Treasury Management Protocol. Stewards execute on‑chain transactions after approvals. The Project Lead coordinates contributors, reporting progress and variances.

Reporting & Closeout: On completion, the Project Lead publishes a report and retrospective to the Governance Forum. Learning is captured for reuse, and the project is formally closed.

Steps: Prospect → Proposed → Planning → Active → Acceptance → Paused → Reflecting → Complete → Cancelled → Declined.

Operations Team Protocol

Metadata
id
RC-protocol-operations-team
name
Operations Team Protocol
description
Lifecycle for operational work streams, including proposal, prioritization, execution, and reporting.
initializationEvent
Operator Leads convene for regular check-ins or infrastructure planning session.
associatedFunctions
operational planning, infrastructure maintenance, resource allocation, program management
associatedRoles
Operator Lead, Steward (oversight), Contributor
relatedMembranes
Operations Team, Steward Council, Project

Purpose: This protocol defines how the Operations Team manages Commons infrastructure, coordinates operational work streams, and responds to emergent needs.

Initialization: The Operations Team is composed of domain-specific Operator Leads. Domains may include Project Review, Member Review, or others as defined. Regular check-ins and planning sessions are scheduled by Operators.

Participants: Operator Leads, supporting contributors, and relevant Stewards for alignment.

Proposal & Approval: Operational needs and improvements are proposed within domains. Operator Leads prioritize based on capacity and urgency. For resource-intensive or cross-domain actions, the Steward Council reviews and approves.

Execution & Funding: Operators coordinate day-to-day execution within their domains. Resource allocation and infrastructure budgets are managed under the Treasury Management Protocol with Steward sign-off where required.

Reporting & Closeout: Operators provide regular status reports to the Steward Council and the Commons Members Assembly. Completed operational initiatives are documented for continuity and future reference.

Steps: Identified Need → Proposal Drafted → Operator Review → Approved / Declined → Implementation → Status Reporting → Retrospective.