Strategy specification
የመሣሪያ፣ የሞባይል ዳታ እና የግንኙነት አውድ: ይህ መመሪያ ለኢትዮጵያ የመዳረሻ ሁኔታ ተዘጋጅቷል።
| Component | Required definition | Evidence |
|---|---|---|
| Market/regime | Symbol, session, trend/range filter | Tagged observations |
| Entry | Price/event conditions | Timestamped signal |
| Invalidation | Logical price level | Pre-order stop |
| Sizing | Cash risk ÷ complete stop loss | Calculation log |
| Exit | Stop, target, time/trailing rule | Order history |
| Pause rule | Drawdown/data/connection trigger | Journal decision |
Validation ladder
- Write immutable rules.
- Use clean historical data without look-ahead.
- Reserve out-of-sample period.
- Add spread, commission, swap and slippage.
- Run walk-forward and parameter stress.
- Forward-test on demo.
- Use smallest live risk and compare actual fills.
Metrics that expose fragility
| Metric | Question |
|---|---|
| Expectancy | Average result after costs? |
| Maximum drawdown | Capital and emotional tolerance? |
| Profit factor | Dependent on few outliers? |
| Trade count | Enough independent observations? |
| MAE/MFE | Are stops/targets evidence-based? |
| Regime split | Does edge survive different conditions? |
Weak-network controls
Use server-side SL, record every ticket, avoid rapid retries and reconcile Orders/History after reconnect. Local trailing stops and EAs stop when the terminal/VPS is unavailable; model that failure explicitly.
Failure conditions
- Costs erase expectancy.
- One parameter change destroys results.
- Loss clusters exceed the limit.
- Live fills materially diverge from test.
- Rules cannot be followed on the actual device/network.
Planning references
Exness cost/margin calculator fields · SL/TP behavior
ተደጋጋሚ ጥያቄዎች
What makes a CFD strategy successful?
Positive after-cost evidence plus controlled drawdown and repeatable execution—not a winning screenshot.
How many indicators are needed?
No fixed number; every rule must add tested information.
Is backtesting enough?
No. Use out-of-sample, demo and small live execution tests.
When should I stop it?
At predefined drawdown, execution divergence or data/infrastructure failure limits.