Trading Risk Playbook

Disclosure requirements, preflight validation, kill-switch configuration, and fallback templates for all trading and prediction market products.

TradingRiskComplianceDisclosure
⚠️ Mandatory disclaimer

All trading, prediction market, and execution-related products on this platform are tooling and educational resources only. They are not investment advice, financial advice, or trading signals. Users are solely responsible for all execution decisions, risk management, and regulatory compliance. Past performance of any strategy or model is not indicative of future results. Nothing in these products or this guide constitutes a recommendation to buy, sell, or hold any financial instrument.

Trading product execution tiers

Trading products are tagged with an execution mode that determines required safeguards:

Research

Analysis, modeling, and hypothesis generation only. No execution connectivity. Lowest risk tier.

Paper Trading

Simulated execution against live market data. No real money at risk. Risk disclosure required before download.

Live Execution

Real execution connectors and order routing. Highest risk tier. Full disclosure + preflight checklist required.

Disclosure requirements

All products with execution_mode: paper or execution_mode: live require explicit risk acknowledgement before download. This is enforced at checkout.

The disclosure acknowledgement records:

  • Product ID and version
  • Timestamp of acknowledgement
  • The disclosure text version that was presented

If the disclosure text is updated (e.g., new regulatory language), re-acknowledgement is required before accessing the updated product version.

Preflight checklist — live execution

Before running any live-execution product, verify each item:

Paper-traded the strategy for a minimum of 30 days with representative market conditions
Defined maximum position size and per-trade risk in the config (never more than you can afford to lose)
Kill-switch tested: confirm the emergency stop halts all orders within 5 seconds
API keys are scoped to minimum required permissions (trade-only, no withdrawal access)
Rate limits confirmed against broker/exchange API documentation
Slippage and transaction cost assumptions validated against actual fills in paper mode
Logging enabled and routed to a persistent store (not just console output)
Regulatory compliance reviewed for your jurisdiction (some products are restricted)
Backup connectivity plan in place if primary API endpoint goes down
Position limits set at the broker/exchange level as a secondary safety layer

Kill-switch configuration

Every live-execution product ships with a kill-switch template. Configure it before your first live run.

# kill_switch_config.yaml
# ---
# Customize thresholds to match your risk tolerance

kill_switch:
  enabled: true

  # Halt if daily P&L drops below this (absolute value or %)
  max_daily_loss: -500          # USD
  max_daily_loss_pct: -2.0      # % of starting capital

  # Halt if drawdown from peak exceeds this
  max_drawdown_pct: -5.0

  # Halt after N consecutive losing trades
  max_consecutive_losses: 5

  # Halt if API error rate exceeds this in a rolling 5m window
  max_api_error_rate: 0.10      # 10%

  # On trigger: cancel_all_orders, close_all_positions, notify
  on_trigger:
    - cancel_all_orders
    - close_all_positions
    - notify: "support@yourdomain.com"

  # Manual reset required before resuming after kill
  require_manual_reset: true

Fallback response templates

Use these in your agent's error handling to produce safe, standardized responses when a trading action cannot be completed:

Signal confidence below threshold
{"action": "NO_TRADE", "reason": "Signal confidence {{confidence}} below minimum threshold {{min_threshold}}", "recommended_next": "WAIT_FOR_CONFIRMATION"}
Kill switch triggered
{"action": "HALT", "reason": "Kill switch triggered: {{trigger_condition}}", "positions_closed": true, "requires_manual_reset": true}
API unavailable
{"action": "DEFER", "reason": "Exchange API unavailable ({{error_code}})", "retry_after_seconds": 60, "open_positions_status": "UNCHANGED"}
Risk limit exceeded
{"action": "REJECT", "reason": "Order rejected: would exceed {{limit_type}} limit ({{current}} / {{max}})", "alternative": "REDUCE_SIZE"}

Regulatory notes

Automated trading is regulated differently across jurisdictions. Some notes:

  • US: Retail forex automated trading requires CFTC/NFA oversight for advisors. Futures require CFTC registration for CTAs managing others' funds.
  • EU/UK: MiFID II / FCA regulations apply. Algo trading systems may require pre-trade risk controls and documentation.
  • Prediction markets: PredictIt, Kalshi, and similar platforms have jurisdiction restrictions. Verify eligibility before use.
  • All: These products are personal use tooling. Running them as a service for others likely triggers additional licensing requirements.

This is not legal advice. Consult a financial or legal professional for your specific situation.

Next steps