> 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/04-how-robindog-works.md).

# 04 How robindog works

RobinDog is built around six connected product modules.

| Module                     | User value                                              |
| -------------------------- | ------------------------------------------------------- |
| Prediction Market          | Trade whether an event will occur.                      |
| Stock Story Page           | See the full narrative around a company or asset.       |
| Story Tree                 | Follow the history of a story and its next branch.      |
| RobinDog Battleground      | Join a side and compete through a priced market.        |
| Conditional Impact Markets | Trade how an event may affect an asset.                 |
| Narrative Combo Positions  | Combine an event view with an asset-direction position. |

New users do not need to understand every mechanism before participating. The simplest path is:

Choose a question → Buy YES or NO → Follow new information → Hold or exit early → Market resolves → Review your record or enter the next branch


---

# 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/04-how-robindog-works.md?ask=<question>&goal=<endgoal>
```

`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.