> 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/18-the-growth-loop.md).

# 18 The growth loop

RobinDog's growth is intended to come from content, trading, and credible settlement together, rather than token rewards alone.

A meaningful story emerges → A resolvable market is created → Battleground forms competing sides → Story Tree organizes history and evidence → Users trade YES, NO, or a combo position → Capital creates a live probability → The market resolves credibly → Users receive records and share cards → The next Story Branch opens

Different content categories serve different roles:

* Pons, memes, and onchain trends support early distribution.
* Equities, company events, and major crypto events establish product awareness.
* Story Trees and user records improve retention.
* Conditional Impact Markets and Narrative Combo Positions create long-term differentiation.

RobinDog will not launch with an 'anything can be predicted' position. Initial markets will focus on events that can materially affect equities, crypto, and broader market prices.


---

# 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/18-the-growth-loop.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.