• subDAOs operate under the following guidelines:

🤝 Reponsibilities

The responsibilities allocated to each subDAO are those delegated from the BAL holder, BAL holder can revoke any or all of these delegated responsibilities through by posting a formal proposal and gaining community consensus.

🧑🏽‍🤝‍🧑🏿  Contributors

Within a subDAO, there are three kinds of contributors:

• Signer (responsible for executing decisions)
• Members (active contributors doing work)
• Observers (contributors who don't do much work - e.g. BAL holders)

Accountability:

• The Signers of each subDAO are accountable to all contributors of the subDAO.
• Ops subDAO is responsible for connection between each working group and provides community interface through reporting of working group progress, milestones and initiatives.
• Ops will formally approve whenever a Signer is added or removed from a subDAO, though it is likely that subDAO has the most visibility into who among the contributors would make a good leader. It should not be Ops making a unilateral decision, but the Signers are ultimately accountable to Ops and Ops is accountable to BAL token holders.
• The Community is responsible for holding the Ops subDAO accountable to reporting and communication transparency.

Notes:

• Non-signers can weigh in, do work, or make proposals but only the signers decide on taking action.
• Social consensus means signers will decide through an off-chain process within their team - it can be as simple as yes/no in the chat.

🚴‍♀️ Cycles

subDAOs operate on quarterly cycles ( starting 1 January, 1 April, 1 July, 1 Oct). Quarterly cycles are used for budget allocation, reporting, goal setting and alignment across the DAO.

A learnings and review document will be created by each funded subDAO at the end of each cycle. These documents will be compiled into one document by the Ops subDAO for posting on the forum. Any unspent resources at the end of the cycle can be rolled over as part of the budget allocation for the next cycle.

🔺 subDAO Formation

• A minimum of three Signers are required and are to be identified for the subDAO
• subDAO powers are to be clearly defined, as these responsibilities are to be delegated by the BAL holders (wider community).