> 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/17-governance-and-security.md).

# 17 Governance and security

RobinDog plans to introduce governance progressively. Early community governance may cover new market categories, Story Tree curation, Creator admission, incentive weights, data-source proposals, and participation in market disputes.

During the protocol's early stages, matters that affect user-fund security should not be controlled entirely by open token voting. These include contract upgrades, major treasury expenditures, admission of new collateral assets, emergency pauses, and core risk parameters.

These powers should initially be protected by public multisignature controls, timelocks, and clear onchain records. The role of community governance can expand as the protocol matures.

RobinDog plans to establish:

* Smart-contract audits.
* A bug bounty program.
* Market risk caps.
* Single-asset exposure limits.
* Oracle anomaly monitoring.
* Emergency pause and close-only modes.
* Multisignature controls and timelocks.
* Public settlement and treasury records.


---

# 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/17-governance-and-security.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.