> For the complete documentation index, see [llms.txt](https://robindog.gitbook.io/robindog-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robindog.gitbook.io/robindog-docs/08-robindog-battleground.md). # 08 Robindog battleground RobinDog Battleground places two competing views in the same market, including company versus company, project versus project, YES versus NO, KOL versus KOL, competing research theses, or different Story Trees. Example Battleground markets include: * Which Pons project will graduate first? * Which crypto project will launch its mainnet first? * Which of two companies will reach a specified revenue target first? * Which related asset will perform better after an event? * Will a project enter the top ten by onchain trading volume within a stated period? Users can join a side, open a position, view leaderboards, and generate a personal results card after the market resolves. Battleground is a public competition in which opposing views can be priced and settled. --- # 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://robindog.gitbook.io/robindog-docs/08-robindog-battleground.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.