> For the complete documentation index, see [llms.txt](https://docs.axiomprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axiomprotocol.io/protocol-design/bootstrap-launch-mechanism/bootstrap-roadmap.md).

# Bootstrap Roadmap

### Launch Roadmap

Week 1-2: Dev signers create demo markets across sports, crypto, and macro categories. Early launch focuses on proving the CLOB trading flow, order book behavior, and market resolution lifecycle.

Week 3-4: Dev signers submit proposals for completed markets to showcase optimistic resolution, challenged resolution, and rewards distribution.

Month 2: Reduce dev activity as organic participation grows and market creation, trading, and governance metrics strengthen.

Month 3-12: Transition to community control with 3-signer termination option and hard 12-month deadline.

### Post-Bootstrap Monitoring

Key metrics tracked after bootstrap:

* Decentralization metrics: market creator diversity, proposal participation, voter distribution (Gini).
* Quality metrics: resolution accuracy, challenge rate, penalty distribution fairness.
* Liquidity metrics: order book depth, trading volume, spread quality, and effective APY.


---

# 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://docs.axiomprotocol.io/protocol-design/bootstrap-launch-mechanism/bootstrap-roadmap.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.