> 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/06-stock-story-page-as-the-narrative-home-for-an-asset.md).

# 06 Stock story page as the narrative home for an asset

Every major company, Stock Token, or crypto asset can become the root of a Story Tree. A Stock Story Page is intended to bring together:

* Company or project fundamentals.
* Prices of related assets.
* Price-feed status.
* Live prediction markets.
* Historical resolutions.
* Upcoming catalysts.
* Relevant research and evidence.
* Community views.
* Related crypto, Pons, or meme narratives.

Users see more than a price chart: they see what is driving the asset and what the market believes will happen next.

A company or asset can be organized across several narrative tracks:

| Narrative track         | Example markets                                                    |
| ----------------------- | ------------------------------------------------------------------ |
| Earnings and guidance   | Will revenue exceed the target? Will annual guidance be raised?    |
| Products and technology | Will the product launch on time? Will sales reach the target?      |
| Policy and regulation   | Will a policy pass, and will it affect the company's business?     |
| Industry competition    | Which company will reach a technology or market milestone first?   |
| Macro factors           | Will rates, inflation, or policy affect the related asset?         |
| Market performance      | Will the asset reach a price or relative-performance target?       |
| Onchain data            | How will Stock Token volume, liquidity, or holder counts change?   |
| Community narratives    | Will related crypto, Pons, or meme activity become a market theme? |


---

# 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/06-stock-story-page-as-the-narrative-home-for-an-asset.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.