From other DAOs as Balancer, there is the role of a Ops Pod with the objective to connect each working group and provide community interface through reporting of working group progress, milestones and initiatives. Ops subDAO is the conductor of the orchestra. This subDAO is responsible for:
For reference, this is the proposal to create the framework of Balancer subDAOs: here
“Ops will formally approve whenever a Signer is added or removed from each 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.
I think we could have a Ops Pod in the Tribe DAO with this role. Some entity responsible for making transparent for everyone the operations of the DAO, as Balancer intend to do here.
In another alternative, the responsibilities could be under Tribal Council but 9 signers is a large group and more difficult to coordinate. A larger group also has some dispersion in accountability. To mitigate that, we need to know specifically the members responsible for each activitiy in Tribal Council.
I believe in the power of multiple small groups with autonomy and accountability.
In the spirit of providing actionable guidelines for governance action; I am recommending the following draft procedures for Nope DAO:
Any user who meets a quorum of more than 5,000 TRIBEs may propose a new action directly on-chain, or via the Fei Protocol snapshot.fei.money with the title-serial number Nope DAO Veto (NDV-xx, Vetoing “summary of pod/council action”), with at least 24 hours, but no more than 48 hours of voting time allotted.
The NDV should clearly state the specific action it is trying to veto, the pod/council which authorized the target action in the first place, and what is the reason for the veto. Permissible grounds for starting a veto can include, but are not limited to:
a. The action will clearly result in immediate PCV losses, or would expose Protocol equity to elevated risks.
b. The action is in clear violation of the stipulations of a passed FIP or violates published guidelines of that specific pod in question.
c. The action will result in clear conflicts of interest or unfairly profit the members of the pod/council that has authorized it.
d. The action contains faulty code or other on-chain vulnerabilities.
Upon the initiation of on-chain Nope DAO action or NDV, the author of the veto or Fei Discord Moderators should promptly start a Discourse forum thread discussing this proposed Veto. This forum thread should be also advertised to the @governance tribe role on discord. The original proposers of the target action should also promptly respond to the accusations levied by the NDV on discourse.
The on-chain action will automatically veto upon receiving 10,000,000 votes. If the NDV snapshot crosses the 10 Million vote quorum, the Guardian Protocol should step in and immediately terminate the target action. The original proposers of the now vetoed action must write a report answering to the Tribal Council why it has proposed such actions and provide details to the decision making process.