okx-live-trading

OKX Live Trading

A live profile binds one strategy, one instrument, one account, and a set of risk budgets. Once enabled it acts on every closed one-minute bar without being asked again.

Read references/lifecycle.md before creating or starting anything.

This spends real money. Every constraint below exists because of a specific way money gets lost, not as ceremony.

Ask before committing real money

On the demo environment, work independently: write, backtest, tune, create a profile, start it, read the signals, stop it. That is a complete verification loop and you should use all of it without checking in at each step.

Before enabling any profile whose environment is live, stop and ask the operator. Nothing in the system will stop you, so this is your responsibility rather than a check you will run into.

State these things and wait for an explicit yes:

• which profile, on which instrument and account
• the entry budget, side budget, and daily loss limit, in USDT
• the backtest behind it, quoting validation-segment figures rather than training ones
• what the demo run showed: how many signals, how many were refused and by which gate
• that starting it commits real money to a strategy that will act without further approval

"Should I start it?" on its own is not asking. The operator needs the numbers in front of them to answer usefully.

If they say yes, start it and report what happened. If they do not answer, leave it stopped — a profile nobody approved should not be trading.

If live_create_profile and live_start are absent from your tool list, the operator has not enabled agent access. Say so and stop; do not reach for trade_place_order to do the same thing by hand.

Workflow

1. Establish the strategy first, through okx-strategy-research: write it, validate it, backtest it, and tune it. A profile cannot be enabled until its exact source has completed a backtest on its exact instrument, so this is not optional.
2. Confirm the market data environment matches the profile you intend to create. Demo and live are separate markets with different prices; desic-okx market env reports which is streaming, and a mismatch is refused at enable time.
3. Choose budgets deliberately and be able to defend each one. live_create_profile requires a rationale from you: which backtest justified this, and why these numbers. Write it for someone reviewing the profile a month later.
4. Call live_readiness before live_start. It lists everything outstanding at once, so you fix the set rather than discovering one blocker at a time.
5. Start on demo. Let it run long enough to produce several signals of more than one kind.
6. Read live_signals and report what actually happened, including the refusals.
7. Read live_audit when diagnosing lifecycle or execution state. Unlike mutable profile/signal rows, these transition events remain after a profile is deleted.
8. Stop with live_stop when the observation is done. Never leave a profile running because it might be useful later. If account-wide state is uncertain, engage live_engage_kill_switch; it persistently stops every profile and blocks all re-enables until an operator clears it.