Live trade setup

Configure per-asset regime confidence and create an ACTIVE LIVE setup with an optional one-shot force first trade. Requests go through this app's API proxy to your Kaizen engine (KAIZEN_ENGINE_URL).

Before a new on-chain proof: cancel other ACTIVE LIVE setups on the engine (stop → release) so only one setup competes for allocation. Repo runbook: docs/internal/LIVE-TRADING-FOLLOW-UP-4-OPERATOR-RUNBOOK.md — VPS script kaizen/scripts/live-setups-list-and-cancel-commands.sh. Use the smallest allocation that still validates (often 0.001–0.005 ETH).

Phase 0 — Force first trade (required for first on-chain BUY)

Leave this on for a one-shot BUY on the next cycle. The engine sends initialStartMode: "FORCE_FIRST_TRADE" and forceInitialTrade: true. Turning it off matches Replit setups that never fired (AUTO+ no forced entry).

Force first trade on LIVE setupPre-checked by default. Uncheck only if you intentionally want normal signals only (AUTO).

Regime confidence (LIVE)

When the gate is on and threshold is 0%, the engine does not enforce a regime-confidence bar (isRegimeConfidenceEnforcing is false). Turning the gate off also bypasses it.

Regime confidence gate enabled

Threshold (0%)

Regime-confidence bypass active for LIVE — related blocking gates are off.

Engine /status (this asset)

Trade setup

Asset list from engine GET /assets when reachable; otherwise all static registry ids from kaizen/src/config.ts (10 rows). Disabled assets are listed but cannot be selected for new setups.

Name

Asset

MethodAllocation (ETH)Default 0.002 for minimal-risk proof runs; increase only if validate/start fails.Ledger idP4-A: optional (GET /allocation-ledgers/:id)