ComputeX Trading Agent Community

The desktop Trading Agent separates external services from strategy rules so providers can be added or replaced without changing the safety contract.

Main local components

• Desktop dashboard and Settings — show status and let the owner choose formulas, providers, schedules, limits, and execution controls
• Broker adapter — reads the selected account, positions, open orders, fills, and submits supported order actions
• Market-data adapter — supplies quotes, candles, scans, and supported market evidence
• Strategy and picker engine — evaluates the selected universe and formula using the available evidence
• Scheduler — owns New York market-time scans, buy cycles, sell checks, VIX refreshes, and reconciliation
• Execution guards — enforce account, position, risk, timing, data-freshness, and owner-controlled Buy/Sell gates
• Reconciliation — compares local state with broker positions, open orders, and fills after start or interruption
• Local storage — preserves approved settings, state, audit evidence, and sanitized diagnostics on the desktop computer

Provider contract

A new broker or data source must implement the same normalized capabilities and explicit error states. Unsupported features must fail closed and be shown clearly; an adapter must not invent a quote, assume an order filled, or treat an unavailable provider as ready.

Adding a provider does not bypass the selected formula, scheduling, position limits, data-freshness requirements, Stop All Trading, or any other execution guard. Broker and market-data readiness are tested separately so a healthy connection cannot hide a failure in another part of the pipeline.

Reliability expectation

Every release should test clean installation, upgrade, restart recovery, credentials-not-configured behavior, market-closed behavior, provider rejection, stale data, missing scans, duplicate-order prevention, partial or rejected orders, reconciliation, and safe shutdown. No read-only test places an order.