Framework overview
How CLOB Forge kits are structured: modules, boundaries, and where product kits plug into the framework.
Architectural boundaries
The framework separates four concerns. Each boundary is swappable behind stable interfaces so product kits can vary without fork drift.
Feeds
Market data, oracle references, and health signals into the runtime
Policy
Gates, sizing, and decision paths (often kit-specific)
Execution
Orders, venue interaction, and fill handling
State
Positions, checkpoints, and persistence needed for safe restart
How product kits use the framework
A product kit is a product-shaped configuration and policy bundle on top of this stack. Kit pages in this book describe operator-facing posture (horizon, guards, tuning hints). Executable defaults and exact parameter tables ship in your artifact and fulfillment materials.
Related reading
Installation: toolchain and reproducible installs
Configuration: env layers and secrets
Dry run: rehearsal before capital
Deployment: supervision and releases
Risk controls: caps and kill switches
Replay and audit: JSONL trails
Polymarket-class context
Operators building Polymarket-class CLOB bots often land here from search. The on-site Polymarket bots guide explains how licensed kits map to this architecture; Products lists buyable SKUs. This GitBook stays the operator reference: install, config, dry-run, deployment, and controls.
Last updated