> For the complete documentation index, see [llms.txt](https://server31.gitbook.io/babel-universe-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://server31.gitbook.io/babel-universe-whitepaper/co-own/validation.md). # Validation After a piece is submitted, it goes into a queue waiting to be validated by the reviewers. Editors are qualified BabelDAO members who know the Babel Universe very well. To become a reviewer, one needs to first be a Tree/Author member and pass a licensing exam (think of it as the written exam for a driver’s license). A reviewer is compensated with $BABEL for each work she validates. The more she validates, the more $BABEL she earns. Reviewers do not judge the artistic quality of a piece but whether it is a valid expansion of the Babel Universe. For example, if a piece contains magic, it will likely be rejected because we are a Sci-Fi universe. All validation actions are recorded on-chain. When a work is reported as wrongly validated, the editors of the work will take a penalty on their licenses which will eventually result in their licenses being revoked. In the current design, each work needs to be validated by 1 reviewer to be posted. Once a work is submitted for validation, all reviewers will see it on their dashboard. The first reviewer of the work will receive $BABEL rewards. First come, first serve. It also takes 1 rejection for a piece to be rejected. The reviewer who rejects the piece is incentivized to leave valuable comments. In this way, once the rejected piece is fixed and submitted again, the reviewer who rejected it will most likely be the fastest one to approve it and get the reward because she has viewed this piece before. Once validated, the piece will be published on BabelUniverse.com and considered an official part of the Babel Universe. --- # 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://server31.gitbook.io/babel-universe-whitepaper/co-own/validation.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.