Go Live

Go-Live Checklist

Live mode should be treated as an operational launch. Review configuration, risk posture, monitoring expectations, and execution realities before enabling it.

Configuration review

  • Confirm strategy settings reflect the behavior you intend to deploy.
  • Review assigned assets and asset-level overrides.
  • Check allocation assumptions and portfolio concentration.
  • Make sure leverage settings are understood at both bot and asset levels.

Risk review

  • Understand what can trigger a close, a hold, or a skip.
  • Review TP/SL behavior, trailing posture, and entry-blocking rules.
  • Confirm that the risk envelope matches the amount of capital being exposed.

Operational review

  • Make sure logs and decision traces will be monitored after launch.
  • Know where run history and lifecycle events are visible.
  • Decide who is responsible for reviewing early live behavior.

Execution review

Live mode introduces fills, delays, pending states, slippage, and reconciliation realities that test mode does not reproduce exactly. Users should expect operational variance once the execution boundary is crossed.

Final readiness checklist

  1. The bot has been reviewed in test mode across multiple cycles.
  2. Allocations and leverage assumptions are understood.
  3. Exit behavior and risk controls have been reviewed.
  4. Monitoring responsibility is clear.
  5. The user understands that live execution is an operational launch, not a reversible experiment.

Live mode is not a casual toggle

The product should treat going live as a deliberate approval step backed by test validation and operator review.

Related Pages

Review first

Validate before you deploy

Test mode, risk review, and operator visibility should come before any live execution posture.