> For the complete documentation index, see [llms.txt](https://wiki.rally.io/rally-io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.rally.io/rally-io/archive/creator-review-council/charter.md). # Creator Review Council - Charter At the start of Rally Network, we used the Rally Snapshot proposal board to post creators for approval on an individual basis with voting open to anyone holding $RLY. At scale, this solution became untenable as the number of inbound creators exceeded the ability to post and vote on dozens of proposals per week. ### Number of Council Members and Nominations The council will initially be comprised of 5 members, with room to add additional members in the future based on scale. Rally Staff shall comprise no more than 2 members of the council to promote community oriented governance. The rest of the council consists of members of the Rally community. At large community member self nominations would be the process to find members. The community will vote on a set of finalists provided a name and a short bio. ## Scope Council will review Creator Coin candidates. In the future, scope may include reviewing previously approved creators. ### Format The council would be organized through a special role + private Discord channel(s). One channel for the list of creators, one channel for the discussion of creators. Creators up for approval would be captured in a privately shared document, such as a spreadsheet, with info such as Name, Bio, and at least one social link for review purposes. ### Voting Council members will vote Yes or No on a candidate by candidate basis. Any council member can request a focused discussion of a creator. A council member can then call for a vote on a single creator should that member procure 1 other member to support, or second, their request. A simple majority (51%) of Yes votes would then be required to approve the creator. Staff members are appointed based on roles related to Creator and Community operations. ### Quorum Quorum for a new creator is 100% of members. Absences/Abstentions will result in a Yes vote. ### Frequency Given current volumes of creators submitted for proposal, creator review will happen across one voting period per week. ## **Council Membership** $RLY is the governance token for voting on this future proposal, and the council members proposal. After approval, council members can be removed by $RLY token holders proposal. The council is not an extension of the company, but rather serves the community of $RLY holders. ### **Time Commitment** Council members are expected to participate in voting operations 5-10 hours per week. ### **Compensation** Selected at large community members would be eligible for compensation for Council membership. Compensation to be $1,000 per month, payable in USDC from the Rally Treasury. Staff, Advisors, and Ambassadors are not eligible for compensation for council membership. ### **Absences** A member who does not actively participate in review and voting sessions will be subject to membership review by the other members of the council. ### **Resignations** If a council member resigns or requires replacement, there will be a call for submissions for a new council member and a Snapshot proposal vote on a select set of candidates. ### **Removing a Council Member** After approval, council members can be removed by $RLY token holders proposal. The council is not an extension of the company, but rather serves the community of $RLY holders. ### Term **L**imits While a sitting community-based council member can resign or be removed through a $RLY Governance vote (via Snapshot proposal), we should consider term limits for sitting members. Member participation will be reviewed every 6 months, with a maximum term of 2 years in limited circumstances (for the sake of continuity and educating new council members). This includes Staff members. Council could ensure some level of ongoing attrition such that there is a mix of experience across council members. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.rally.io/rally-io/archive/creator-review-council/charter.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.