GHOSTGUARD

Risk Controls for Automated Prop Firm Trading

GhostGuard applies enforceable checks to accepted Ghost instructions and selected Copy Trader accounts. Each control below names where it runs and what it does when triggered.

Controls vary by workflow and platform. They do not guarantee against a prop-firm breach, slippage, gaps, rejection, disconnection or direct broker activity.

Control Matrix: Trigger, Action and Scope

ControlTriggerActionVerified scope
Configured stop and targetAn accepted entry includes configured protection.Ghost sends the supported stop/target instructions through the selected order path.Platform and order-path qualified
Unprotected-entry refusalA QC Auto market entry requires a stop that cannot be placed.The QC Auto entry is rejected instead of intentionally opening without the required stop.QC Auto market-entry path
Trading windowA signal arrives outside the ticker’s configured session.The signal is rejected before entry execution.Ghost signal-processor path
Max daily tradesA ticker reaches its configured daily trade count.Additional ticker signals are logged and skipped.Ghost ticker signals, not manual broker orders
Cross-ticker collisionAnother strategy targets the same account and underlying symbol in a conflicting path.The conflicting entry is blocked, including a concurrent-race recheck.Ghost shared account/symbol path
Global kill switchThe platform kill switch is active when a new entry arrives.New incoming entries are rejected. Exit handling is evaluated separately.Ghost entry signal path
Position reconciliationGhost no longer sees a previously tracked broker position.State closes only after the confirmation gate, not after one absent read.Supported broker reconciliation paths
Daily loss / profit controlsA selected account reaches its configured DLL or DPT condition.The Copier applies its documented account control; direct broker trading is outside that application lock.Copy Trader: Tradovate and ProjectX UI-supported accounts

Broker-side protection

A supported resting stop or target is an order at the broker. Availability and behavior depend on the selected integration, account and order path. It should not be described as universal across all eleven platform integrations.

Application-side controls

Trading windows, count gates, collision checks, kill switches and Copier account controls can reject, skip or lock activity inside their documented QuantCrawler path. They do not necessarily block manual orders placed directly at a broker.

Before, During and After a Trade

Before

Check the trading window, daily count, global entry switch, collision state and any required QC Auto protection.

During

Inspect the actual broker response and confirm that supported stop/target instructions were accepted for the account and order path.

After

Reconciliation confirms broker-side closes across multiple reads before changing tracked state. Review account outcomes rather than assuming a request completed everywhere.

Prop-Firm Setup Checklist

  • Confirm the firm's current automation and copying rules.
  • Map news restrictions and the required session close.
  • Check contract limits, account role and supported connection.
  • Distinguish a daily loss limit from trailing drawdown.
  • Document the broker-side emergency flatten procedure.
  • Verify which control applies to each account and rail.

GhostGuard FAQ

Does GhostGuard guarantee an account cannot breach?

No. Gaps, slippage, rejected orders, connection failures, manual broker activity and prop-firm rules can still affect an account. GhostGuard applies the scoped controls described here; it does not define guaranteed maximum downside.

Are stops always held at the broker?

Only where the selected platform and order path support broker-side stop instructions. An application-side rejection, pause or lock is different from a resting broker order.

What happens if a required stop cannot be placed?

The verified QC Auto market-entry path refuses the entry when its required broker stop cannot be placed. Do not generalize that behavior to every Ghost integration or order type.

Which accounts support DLL and DPT?

The current Copy Trader risk interface documents per-account DLL/DPT controls for Tradovate and ProjectX accounts. Confirm current rail behavior before relying on it.

Does a Copier lock block direct broker trading?

Not necessarily. Application controls govern their documented QuantCrawler path and should not be described as blocking orders placed directly at the broker.

What does the global kill switch stop?

The verified main signal path rejects new incoming entries while the switch is active. Exit behavior is handled separately so a new-entry block is not marketed as a universal order block.

Add Risk Controls with Ghost

Connect a supported account, then send Ghost's required JSON webhook payload from TradingView or another compatible alert source.