Section 0. Background

The identifier of the DAO is SOMEEOFFICIAL, deployed on the SnapShot DAO Ecosystem the following URL identifier https://vote.somee.social, from now on referred to as the "DAO" and backed by the Ethereum Blockchain for token values. 

The DAO is a "decentralized autonomous organization," an unincorporated association of individuals, entities, associations, and other persons or groups of persons.

This agreement exists to enumerate the shared mission, principles, and governance guidelines that bind the DAO's members together and the operating rules of the DAO. 

Section 1. RFC 2119 compliance

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Section 2. Immutable guidelines

Admins/Owners SHALL NOT amend the guidelines in this section. If any other policies in this Agreement conflict with these immutable guidelines, the immutable guidelines SHALL take priority for enforcement purposes. These guidelines apply to all proposals submitted to the DAO. 

1. Proposals MUST be governed by this Agreement, or a future version of this Agreement as modified within the bounds of the Agreement.
2. Disputes over a proposal relying on this Agreement MUST be resolved by the dispute resolution in our main TG chats with the community, or as comments on the proposal.
3. Proposals MUST NOT disproportionately benefit a majority of Token Holders voting on a proposal over the minority. Ergo, proposals SHOULD ONLY affect all people on the project, not disproportionally affect only one portion.
4. Proposals MUST ONLY affect the project, not the company level. Company level decisions are decided by the SHAREHOLDERS of the company, and do not affect the project as a whole.

Section 3. Mutable guidelines

Admins/Users MAY amend the guidelines in this section. These guidelines apply to all proposals put forth by the DAO. 

1. Proposals MUST be accompanied by an accurate American English-language Justification for the proposal. Typos in the Justification SHALL be allowed if they do not substantially alter the meaning of the proposal. Each Justification MUST be referred to in the on-chain source code or transaction data of the proposal by the content-addressed location of the Justification on the public IPFS network, and the Justification MUST be accessible via the public IPFS network for as long as the proposal is open for voting and/or in effect. If a Justification becomes temporarily inaccessible via the public IPFS network, and its proposal is challenged under this guideline, then guardians SHOULD block the proposal if they have reason to believe the Justification was inaccessible at the time that the proposal was challenged. Alternatively, the Justification MAY be encoded directly into the on-chain source code or transaction data of the proposal so that the Justification remains human-readable and accessible as long as the Ethereum blockchain itself remains publicly available. The Justification MUST include the following information:
   • The name(s) and/or username(s) of the author(s) of the proposal. The author(s) SHOULD be the primary point of contact for any questions or comments regarding the proposal.
   • The author’s preferred contact method, in case anyone has questions or comments regarding the proposal.
   • An accurate summary of the proposal in 280 characters or less.
   • A rationale section detailing the author’s reason(s) for creating the proposal.
   • An accurate, long-form description of what the proposal will do if enacted.
   • A section acknowledging by title and author(s) any similar or related prior work known to the proposal author(s).
   • If the proposal amends one or more Network contracts, then a security audit report of the Network contract amendment MUST be included in the Justification. This security audit report MUST be produced by a third-party security auditor and remain publicly accessible for as long as the amendment is in effect. The third-party security auditor MUST NOT have any financial relationship to the proposal author(s) aside from their being hired to perform the security audit.
2. Proposal Justifications MUST NOT contain directly or by direct link any Non-consensual Imagery (NCI), Child Abuse Imagery (CAI), malware, spyware, or material that is owned via Copyright by someone other than one of the proposal authors (unless the use of said Copyright material is permitted by the copyright owner or otherwise protected under Fair Use standards).
3. Participation - DAO proposals must pass a minimum quarum or participation level before their suggestions are binding. For the purposes of most propoals, this is equal to about 1/2 of the circulating supply of the underlying token.

Section 4. Definitions

Any words or phrases not explicitly defined here SHALL be determined by either the Merriam-Webster Dictionary (https://www.merriam-webster.com/) or the Merriam-Webster Law Dictionary (https://www.merriam-webster.com/legal). In cases where a word or phrase appears in both the Dictionary and Law Dictionary, the Law Dictionary definition SHALL be used by the reader. In cases where a word or phrase is not explicitly defined here or in either of the dictionaries specified above, the reader MAY use the definition most reasonable to the reader.

• Token Holders - The parties holding the native token of the DAO. 
• Governance Executor - A DAO app that enables members of an organization to interact with other smart contracts on behalf of the organization, as if it were the organization itself performing the interaction. All transactions executed by the DAO are performed by this app.
• Ethereum blockchain - The blockchain is referred to as “Ethereum” by the owner of the Ethereum trademark, the Ethereum Foundation (Stiftung Ethereum).
• IPFS network - A peer-to-peer hypermedia protocol, whose project website is located at https://ipfs.io. The public network makes files accessible to any internet-connected device running a compatible implementation of the IPFS software.
• Network contract - The computer-interpreted source code of a smart contract governed by SOMEE holders.
• Network parameters - The current parameters of smart contracts governed by SOMEE holders, which can be modified without amending the source code of the smart contract itself.
• Proposal - A proposal is any suggested amendment to the Network contracts, Network parameters, or the Agreement of the SoMee Network.
• RFC 2119 - A technical standard for indicating requirement levels, the canonical version of which is located at https://tools.ietf.org/html/rfc2119.
• Smart contract - a software program deployed to the Ethereum blockchain.