> 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/12-resolution-exceptional-events-and-fund-protection.md).

# 12 Resolution exceptional events and fund protection

RobinDog uses different resolution methods for different market types.

| Market type                    | Primary resolution source                                            |
| ------------------------------ | -------------------------------------------------------------------- |
| Stock Token or crypto price    | Chainlink and other market data specified in advance.                |
| Onchain event                  | Smart-contract and blockchain state.                                 |
| Company event                  | Company financial reports, announcements, or specified filings.      |
| Macro or policy event          | A government body or authoritative institution specified in advance. |
| Event requiring interpretation | Preliminary resolution followed by a challenge period and review.    |

RobinDog plans to establish market-status, data-source-status, and resolution-history pages, along with challenge and refund records, contract and permission disclosures, and reward and treasury records.

A market may be paused or placed into close-only mode if:

* Price data has not updated for an extended period.
* Robinhood Chain or its sequencer experiences an incident.
* The related asset is halted.
* A corporate action changes the relevant price basis.
* The event is formally postponed.
* The market rules can no longer be satisfied.
* A related trading venue loses the liquidity required for the market.

The market will then resume, be extended, be cancelled, or issue refunds under rules published in advance.


---

# 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/12-resolution-exceptional-events-and-fund-protection.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.