> 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.md). # Creator Review Council The Creator Review Council exists to review and vote on all new Creator Coin candidates, with an expanded scope in the future. The Creator Review Council is made up of Rally staff and at-large community members. The Creator Review Council is a function of Rally Governance ensuring that the community participates in voting on candidates for Creator Coins. All members must be holding (or vesting) $RLY as that is the governance token for Rally Network. ## Process In cooperation with the BD team, Council members are provided access to a spreadsheet with information about the current list of candidates after their applications have been reviewed by the Creator Applications team. 1. The council is presented with a new batch of candidates on Mondays (by 12pm PT) via private Discord channel. 2. The council then has until 5pm PT on Wednesday to review and vote on candidates. 1. Any discussion on a particular candidate to occur in the private Discord channel. 2. If a member does not vote in a particular cycle, their vote will default to Yes. 3. After the voting period has passed, the list of candidates is published to a public, view-only channel on Discord. Coin launch date will not be provided. ## **Voting** A simple majority (51%) of Yes votes is required to approve the creator. ### Quorum New creator: There is no defined quorum as member votes will default to Yes if a member is unavailable or otherwise abstains from voting. ### **Majority No Decisions** Should a candidate receive a majority of No votes, the candidate will need to be contacted with a reason and explanation. --- # 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.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.