> For the complete documentation index, see [llms.txt](https://crypto-outlaws.gitbook.io/crypto-outlaws-roadmap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crypto-outlaws.gitbook.io/crypto-outlaws-roadmap/core-roadmap.md).

# Core Roadmap

The core roadmap for Crypto Outlaws explains how events will unfold as we work to bring our core poker playing technology to life - regardless of how many NFTs are sold. Only aspects of the project effected by the amount off NFTs sold is how quickly we can develop the technology, which features we can afford to build on top of the underlying tech, and what point we begin DAO formation and further scaling. Not whether or not we build the poker playing tech itself.

This section outlines the general progression of the project from beginning to end. Starting with an idea, evolving all the way into a full-blown product for casino games that can be used safely and securely by hundreds of thousands or even millions of people from all across the world.

![](/files/ogbt2FjRE2Dx3IooHSo6)


---

# 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://crypto-outlaws.gitbook.io/crypto-outlaws-roadmap/core-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.