AKA Operations Silo

Role within YAM

The Gov-Ops Council has 2 main roles within the DAO:

1. The first is to facilitate and guide the high level operation of YAM to vet and fund Silos, Grants, and Projects (Consensus Phase as described here In this role it is not a gatekeeper. It makes recommendations and interpretations of the rules as ratified by the governance process. One could think of it like YAM’s version of the USA’s Court System, which does not make laws, but interprets and clarifies them.
2. The second role is to create and execute on-chain transactions from approved governance proposals (Execution Phase as described here). This is a functional and oversight role. Common, simple transactions and actions that the DAO performs on a regular basis are included in this role, as well as reviewing and calling other contracts that may be created by project silos.

Goals

The goals that the Governance council should aim to achieve are:

1. Oversee the governance process and assure that it is clear, legible, fair, and accessible, and that the standards approved by the DAO are being followed.
2. Coordinate on-chain transactions and assure that interactions with the treasury run smoothly.
3. Review on-chain code written by Silos that will interact with the treasury.

Scope of Work

Code and Smart Contracts

• Routine, pre-approved interactions with the YAM governance contracts and treasury should be the main scope of work for the developers putting together the on-chain transactions. What defines a “routine” transaction should be defined and publicly stated with “off the shelf” code that can be plugged into the contract. Testing the contract also falls into this scope.
• Code that falls outside of this classification is the responsibility of the Silo or Grantee that is requesting it’s inclusion. They should write and test the required code and either implement it in their own deployed contract that can be called by the monthly on chain transaction, or they should coordinate with the Gov-Ops silo to include it directly into the main proposal contract.
• Review of the code and tests and coordinating how it comes together is part of the scope of the Gov-Ops Council.
• Successful Execution of the contract is part of the scope of the Gov-Ops Council.

Governance Coordination

• Communicate with applicants and community members to clarify the process to apply for funding from YAM.
• Make recommendations about the completeness of applications for funding. This entity is not empowered to judge the merit of a proposal, but should give guidance on whether the application is complete and follows approved standards.
• Manage bookkeeping and governance flows. Collate approved consensus actions into one location used as a source of truth for creating on chain execution transactions.