# Documentation home

Public operator manual for CLOB Forge **licensed distribution kits**: installation, configuration, dry-run, deployment, and controls. The same material is linked from your fulfillment email. **Browsing this book does not require login.**

## Who this manual is for

Technical operators who run self-hosted automation against prediction-market CLOBs (for example Polymarket-class venues). You should be comfortable with env-based configuration, process supervision, and reading audit trails before live capital.

## How this book is organized

| Section             | Contents                                                            |
| ------------------- | ------------------------------------------------------------------- |
| **Welcome**         | This home page and the on-site Docs assistant                       |
| **Getting started** | Prerequisites, first dry-run, delivery and troubleshooting          |
| **Framework**       | Shared architecture, install, config, dry-run, deploy, risk, replay |
| **Shells**          | Product-specific notes for each kit in the catalog                  |
| **Licensing**       | Permitted use and `.lic` file format                                |
| **Releases**        | Versioning and how we communicate changes                           |

**Purchased a kit?** Product-specific setup and reference ship with your **artifact and fulfillment email**. This GitBook space is the canonical framework and operator reference for every kit.

**Prefer chat-style lookup?** The site’s [Docs assistant](https://clobforge.com/help) searches this book. See [Docs assistant on the site](/welcome/docs-assistant.md) for scope and limits.

## Quick links

* [Getting started](/getting-started/getting-started.md): prerequisites and first dry-run
* [Delivery, support, and troubleshooting](/getting-started/delivery-and-troubleshooting.md): email fulfillment, missing mail, license checks
* [Framework overview](/framework/overview.md): architecture and boundaries
* [Docs assistant on the site](/welcome/docs-assistant.md): what `/help` is and is not
* [Licensing overview](/licensing/overview.md): permitted use
* [License file format (v1)](/licensing/license-format.md): offline `.lic` verification

**Marketing site:** [clobforge.com](https://clobforge.com) · [Products](https://clobforge.com/products) · [Automation guide](https://clobforge.com/prediction-market-bots)

## Discovery from search

If you arrived while comparing **prediction market bots**, **Polymarket CLOB automation**, or **self-hosted trading infrastructure**, the commercial site explains [how licensed kits fit](https://clobforge.com/prediction-market-bots) and lists [buyable products](https://clobforge.com/products). This GitBook is the framework and operator manual after you have an artifact and license file.

**Indexable focus:** section titles in this book target operator tasks (install, dry-run, deployment, risk). Cross-links to the storefront above are intentional so readers can move from research to purchase without confusion.

***


---

# Agent Instructions: 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.clobforge.com/welcome/readme.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.