All orders
Rules
Specification
Developer Brief — Strategy Philosophy and Risk Approach
When implementing the trading strategy, the choice of method or setup logic is fully up to your technical preference — whether it’s trend-following, mean-reversion, scalping, or SMC-based. What truly matters is maintaining a balance between profit potential and long-term capital safety. The priority should always lean towards safety and consistency over aggressive profit-chasing.
In trading automation, the goal is not to win every trade but to minimize exposure on the losing side. A safe system must focus on capital preservation first, ensuring that no single loss or cluster of losses can significantly damage the account equity. Profitability is only meaningful when it is sustainable. Therefore, the logic and parameters should be designed with the following principles in mind:
-
Risk Management Above All:
Every trade must have a predefined stop loss and position sizing based on percentage risk per trade (e.g., 1–5%). The code should ensure this is non-negotiable, regardless of signal strength. -
Controlled Trade Frequency:
Avoid overtrading. Even a highly accurate strategy can fail if it opens excessive positions without considering volatility and margin constraints. -
Priority on Drawdown Reduction:
Optimize for minimal drawdown, not just high win rate. A steady 10% monthly growth with 5% drawdown is far more valuable than 40% growth with 30% drawdown. -
Loss Containment and Recovery Logic:
Include conditions that pause new entries after consecutive losses or adapt lot size dynamically to protect equity.
Ultimately, the developer’s implementation should reflect a "safety-first architecture" — where profits come as a byproduct of disciplined execution, robust stop management, and risk control. The trader can choose any entry strategy, but the underlying engine must ensure minimal damage during losing streaks and maintain long-term capital survival above all else.