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 searches this book. See Docs assistant on the site for scope and limits.

Quick links

• Getting started: prerequisites and first dry-run

• Delivery, support, and troubleshooting: email fulfillment, missing mail, license checks

• Framework overview: architecture and boundaries

• Docs assistant on the site: what /help is and is not

• Licensing overview: permitted use

• License file format (v1): offline .lic verification

Marketing site: clobforge.com · Products · Polymarket bots guide

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 and lists buyable 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.

---

Maintainer: Git sync

1. In GitBook, connect this repository and set the content / root directory to the gitbook/ folder (so SUMMARY.md and .gitbook.yaml are at the root of the sync).

2. Set NEXT_PUBLIC_DOCS_URL on your deployment host (for example Netlify) to your published GitBook URL (no trailing slash), e.g. https://docs.clobforge.com or https://<org>.gitbook.io/<space>/.

3. Edit Markdown here in gitbook/; avoid editing the same pages in the GitBook web editor while Git sync is two-way, or you may get merge conflicts.

Canonical public URL for redirects and emails is configured in the app via NEXT_PUBLIC_DOCS_URL (see .env.example).