> 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/07-story-trees-that-keep-narratives-moving.md). # 07 Story trees that keep narratives moving Real market narratives are rarely determined by a single event. For a technology company, the story may unfold as follows: **Product launches on time → First-month sales hit target → Quarterly revenue grows → Annual guidance rises → Related asset outperforms its benchmark** Conventional prediction markets often scatter these questions across separate pages. RobinDog connects them through the Story Tree. A Story Tree may include: * Historical nodes that have already resolved. * Event nodes currently trading. * Future nodes that have not opened. * Conditional branches created by different outcomes. * Related asset-impact markets. * The history of changes in market probability. * Evidence supporting both sides. When a market resolves, its outcome can become the condition for the next Story Branch. **Events end. Stories continue.** #### Relationships Between Markets A Story Tree connects related questions without automatically combining their collateral or settlement obligations. Each tradable node has its own rules, collateral asset, resolution source, and settlement conditions unless a different structure is explicitly defined. An outcome at one node may activate a later branch or satisfy another market’s prerequisite. It does not determine every related market’s result. Prices across separate nodes should not be added together or interpreted as a joint probability without a defined model. #### Story Rollover After a market resolves, users may: * Withdraw their funds. * Continue following the Story Tree. * Allocate part of their funds to the next node. * Receive an alert or early access to the next market. * Carry forward their personal prediction record. * Earn non-transferable Story badges or points. At the initial platform launch, RobinDog will prioritize points, badges, and public performance records rather than issuing a separate token for every Story Tree. Moving settlement proceeds into another Story Tree node requires a new user instruction or a separately authorized rollover arrangement. Following a story does not automatically commit funds to its next market. --- # 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/07-story-trees-that-keep-narratives-moving.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.