> 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/whitepaper/architecture-overview/market-architecture.md).

# Market Architecture

Axiom’s markets use a CLOB backed by Conditional Tokens.

Each market stack includes:

* a logical market definition shown in the app
* one or more binary `AxiomCTFMarket` contracts underneath
* ERC-1155 outcome positions in `AxiomConditionalTokens`
* an order book managed offchain
* onchain settlement through `AxiomCTFExchange`

For users, this means one market page can represent a clean product experience even when multiple binary contracts sit behind the scenes.

At resolution, the market contract:

* receives the finalized outcome
* reports payouts to Conditional Tokens
* enables winning position redemption

The exchange handles trade settlement and fees before that point. Redemption is the final conversion of winning tokens back into collateral.

This design keeps Axiom auditable and composable while supporting deeper liquidity and more flexible position management than a pool-based market model.


---

# 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:

```
GET https://docs.axiomprotocol.io/whitepaper/architecture-overview/market-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
