Kambria DAOs – Governance Model Implemented on XDAO

Kambria DAOs use XDAO as the primary governance infrastructure to support decentralized decision-making, proposal management, and on-chain execution.

This page describes how governance is structured and implemented in practice, including the roles of governance tokens, voting processes, and the balance between on-chain mechanisms and off-chain coordination.

Governance Objectives

The governance model is designed to:

• Enable transparent and auditable decision-making

• Balance capital contribution, active participation, and long-term alignment

• Support both technical execution and real-world operations

• Allow DAOs to evolve their rules through proposals rather than fixed assumptions

Governance is treated as an operational tool, not an abstract mechanism.

Governance Infrastructure: XDAO

XDAO provides the core on-chain components for Kambria DAOs, including:

• DAO creation and registry

• Governance Token (GT) issuance

• Proposal creation and voting

• Quorum enforcement

• Execution of approved actions

Kambria builds additional workflows and smart contracts around XDAO to support DAO-specific needs, but governance decisions are anchored on-chain via XDAO.

Governance Tokens (GT)

Each Kambria DAO issues its own Governance Token (GT) upon creation.

Purpose of GT

GT is used to:

• Propose governance actions

• Vote on DAO decisions

• Approve or reject key changes

• Signal long-term commitment and responsibility

GT represents governance rights, not financial ownership.

GT Allocation

Initial GT allocation is defined at DAO creation and may include:

• Organizer (Kambria)

• Initiator or Dev Partners

• Strategic partners

• Core contributors (if applicable)

GT allocation reflects:

• Responsibility for execution

• Governance participation expectations

• Long-term alignment with the DAO’s objectives

GT distribution can be adjusted later through governance proposals.

Proposal Types

Kambria DAOs use proposals to govern both on-chain and off-chain actions.

Typical proposal categories include:

• Governance configuration
  • Quorum changes

  • Voting period adjustments

  • Partner onboarding or removal

• Token-related actions
  • Creation of DAO LP tokens

  • Token sale parameters

  • Vesting or allocation updates

• Operational decisions
  • Milestone approvals

  • Partner payments

  • Budget releases

• Strategic direction
  • Commercialization approaches

  • Expansion to new markets

  • Adoption of new workflows or tools

Each proposal includes a description, voting parameters, and execution logic where applicable.

Voting and Quorum

Voting Process

• Proposals are submitted by GT holders

• Voting is conducted on XDAO

• Votes are weighted by GT holdings

• Voting periods are predefined per DAO

Quorum

Each DAO defines a quorum threshold (e.g. 45–70%) that must be met for a proposal to pass.

Quorum rules ensure that:

• Decisions reflect meaningful participation

• Governance is not controlled by inactive holders

• Critical changes receive sufficient consensus

Quorum values can be modified via governance proposals.

On-Chain Execution and Off-Chain Actions

Not all governance decisions are fully executable on-chain.

Kambria DAOs distinguish between:

• On-chain execution
  • Token creation

  • Contract deployment

  • Automated payments

  • Revenue distribution

• Off-chain execution
  • Development work

  • Service delivery

  • Manufacturing

  • Community programs

For off-chain actions:

• Governance approval authorizes execution

• Results are reported back to the DAO

• Accountability is maintained through documentation and review processes

Role of Kambria as Organizer

Kambria acts as the DAO Organizer, with responsibilities including:

• Designing governance frameworks

• Developing and maintaining smart contracts

• Coordinating partners and workflows

• Supporting proposal execution

• Ensuring documentation and transparency

Kambria does not unilaterally override DAO decisions.
Organizer authority is constrained by governance rules and proposals.

Governance Evolution

Governance rules are not fixed.

Kambria DAOs are designed to:

• Start with practical, simple governance

• Evolve rules as participation grows

• Adjust token distribution and voting logic over time

• Introduce additional decentralization gradually

This approach supports real-world execution while maintaining long-term decentralization goals.

Relationship to Other Framework Components

• The Model section defines why governance exists and how value is structured.

• This page explains how governance is implemented using XDAO.

• The Smart Contracts & Workflows section documents the technical execution of approved decisions.

Together, they provide a complete view of governance from principle to implementation.

Summary

Kambria DAOs implement governance using XDAO to ensure:

• Transparent decision-making

• Clear accountability

• Flexible evolution

• Alignment between contributors, partners, and communities

This governance model enables Kambria DAOs to co-own and scale innovations responsibly across diverse domains.