Bot factory

The bot factory is where a graduated strategy becomes a running container. Each bot wraps one strategy's configuration, runtime settings, and live state, and runs it on the schedule and execution mode you assign. The page lists every bot, shows its status, and gives you the start, stop, clone, and delete controls that govern its lifecycle.

This is an operator surface. It sits at the end of the pipeline: a strategy earns its way here by surviving the gauntlet and clearing the promotion gates, and only then does it warrant a deployed container. The bot factory does not invent strategies or relax any gate — it operates the ones that already passed.

What a bot is

A bot is a deployed strategy container — a running instance of a lifecycle strategy. It bundles:

• The strategy configuration (symbol, timeframe, parameters).
• A container template and runtime settings chosen at deployment.
• Live state: open positions, the trade ledger, and the decision history the bot accumulates as it runs.
• A version history, so a configuration change can be compared against what ran before.

The same underlying container also appears as a strategy container on the live trading page and in the strategy lab detail view. The bot factory is the operator-focused view: it is about the fleet — which bots exist, which are running, and the lifecycle actions on each — rather than the chart-level monitoring you get on the trades page.

Where it lives in the UI

The factory is two routes:

• /bot-factory — the bot list. Each row shows the bot, a status badge, and action buttons. A kill-all control stops the whole fleet at once.
• /bot-factory/[id]/editor — the bot editor. Create a new bot from a template, clone an existing one, configure the container image and runtime settings, and deploy.

Every action on these pages is operator-gated. The backend requires an operator key (FORVEN_OPERATOR_KEY) on the /api/bot-factory/* endpoints, so the factory is unavailable to read-only sessions.

Steps: deploy a bot

You deploy from the editor after a strategy has already cleared the gauntlet and its promotion gates. The factory is the deployment step, not a shortcut around earlier stages.

1. Open /bot-factory and review the existing fleet so you do not duplicate a running strategy.
2. Click New (or Clone on an existing bot) to open the editor at /bot-factory/[id]/editor.
3. Select a template from the template list. Templates define the container shape the bot runs in.
4. Configure the container image and runtime settings for the bot.
5. Confirm the strategy configuration the bot will run.
6. Deploy. The bot appears in the list with its status badge.
7. Click Start on the new bot to begin its run; use Stop to pause it.

What you'll see

After deploying, the bot list shows the new bot with a status badge (for example, a running or stopped indicator) and its action buttons. Open the bot to inspect its trades and positions as it runs. Because beta builds lock execution to paper, a started bot simulates against the live feed rather than placing real orders on the exchange — see paper trading and execution modes for what that means.

Lifecycle actions

The factory exposes the full lifecycle of a deployed container. Each maps to an operator-gated endpoint under /api/bot-factory:

Clone copies an existing bot's configuration into the editor as a starting point, so you can deploy a variant without rebuilding it from scratch. Beyond trades and positions, the bot factory router also tracks each bot's decisions and versions, including a version diff, so you can audit what a bot chose and how its configuration changed over time.

Inspecting a bot from the shell

Every factory action is an authenticated HTTP call against the local API (default 127.0.0.1:8003). To list the fleet from PowerShell with an operator key:

$headers = @{ "x-operator-key" = $env:FORVEN_OPERATOR_KEY }
Invoke-RestMethod -Uri "http://127.0.0.1:8003/api/bot-factory/bots" -Headers $headers

To start a specific bot:

Invoke-RestMethod -Method Post `
  -Uri "http://127.0.0.1:8003/api/bot-factory/bots/$botId/start" `
  -Headers $headers

The UI does the same calls for you; the shell is useful for scripting or for confirming state when a panel looks stale.

Caveats

• Operator-gated. Every bot-factory action requires the operator key. If the API is configured with FORVEN_AUTH_REQUIRED=true, both FORVEN_API_KEY and FORVEN_OPERATOR_KEY must be set or the backend refuses to start.
• Paper-locked in beta. Beta builds hard-lock execution to paper. A running bot does not place real orders on HyperLiquid; it simulates against the live feed. Treat any session figures as illustrative, not as realized results.
• Deploy, don't shortcut. The factory operates strategies that already passed the gauntlet and the promotion gates. It is not a way to skip robustness testing — a bot is only as sound as the strategy inside it.
• Kill-all is a blunt instrument. The kill-all control stops every bot in the fleet. For position-level safety controls — drawdown limits, the kill-switch, and circuit breakers — use the risk & safety page instead.

Related

• Live trading — monitor positions and force-close from the chart workspace.
• The strategy lab — where a strategy is built, tested, and made ready to deploy.
• The pipeline — the full lifecycle a strategy travels before it earns a bot.
• Risk & safety — drawdown gauges, circuit breakers, and the kill-switch.