What is the DCA observation lifecycle?
The DCA observation lifecycle is the full sequence a DCA order follows after it hits its price deviation trigger but is temporarily held by the Volatility Gate instead of being placed immediately.
Instead of firing instantly, the order enters a controlled monitoring phase where market momentum is evaluated before execution.
This lifecycle ensures DCA orders are placed into stabilizing markets, not accelerating ones.
๐ High-Level Lifecycle Overview
A DCA order under Volatility Gate passes through these stages:
- Deviation Triggered
- Momentum Evaluation
- Observation (Held State)
- Cooldown / Reversal Detection
- Release (Order Placed)
- Timeout Safety Release (if needed)
Each stage is deterministic and logged.
๐น 1๏ธโฃ Deviation Triggered
The lifecycle begins exactly the same as traditional DCA.
Example:
- Long trade
- Deviation = 7%
- Price drops -7% from last entry
At this point, the DCA trigger condition is satisfied.
Howeverโฆ
Instead of immediately placing the order, the system passes control to the Volatility Gate.
๐น 2๏ธโฃ Momentum Evaluation
The Volatility Gate calculates smoothed movement using recent 1-minute klines:
- First-half average vs second-half average
- Live price included
- Noise filtered
The system determines:
- Is the move normal?
- Or is it explosive?
If movement is below explosive threshold:
โ Gate CLEAR โ DCA placed immediately (Lifecycle ends here โ behaves like fixed DCA)
If movement exceeds explosive threshold:
๐ญ Gate HELD โ Order enters observation
๐น 3๏ธโฃ Observation State (Monitoring Phase)
The order is now:
- NOT placed
- NOT cancelled
- NOT forgotten
It is held in a structured observation queue.
During this phase:
- The system polls every 60 seconds
- Recalculates smoothed momentum
- Tracks volatility direction
- Monitors time spent in observation
Think of this as a cooldown watch mode.
The bot is waiting for market instability to normalize.
๐น 4๏ธโฃ Cooldown / Reversal Detection
Every 60 seconds, the system checks if one of the release conditions is met:
โ Neutral Condition
Adverse momentum falls below neutral threshold (e.g. 0.5%)
Meaning:
- Selling pressure is slowing
- Crash momentum is weakening
- Market is stabilizing
โ Reversal Condition
Momentum flips back toward trade direction (e.g. -0.3%)
Meaning:
- Price has started moving back
- Exhaustion likely occurred
- Reversal confirmation detected
To avoid false signals:
- Two consecutive qualifying readings are required
- If volatility spikes again, the streak resets
This prevents releasing during temporary pauses in a continuing crash.
๐น 5๏ธโฃ Release (Order Placement)
When confirmation criteria are satisfied:
- The DCA order is placed at live market price
- Not at the old deviation trigger price
This is critical.
Because often:
- Price has moved further
- Or stabilized near the low/high
- Or begun recovery
The release is logged as:
๐ DCA Release [cooled] or ๐ DCA Release [reversal]
The lifecycle ends here.
The order now behaves like any normal DCA order in the strategy.
๐น 6๏ธโฃ Timeout Safety Release
Markets can sometimes remain highly volatile for extended periods.
To prevent indefinite blocking:
If max_observation_minutes is reached:
โ Force Release occurs
The DCA order is placed regardless of current volatility.
This ensures:
- Strategy continuity
- No permanent order suppression
- Predictable system behavior
๐ Timeline Example
Example scenario:
Minute 0: Price hits -7% โ Trigger Minute 0: Smoothed movement = -4.2% โ HELD Minute 5: Momentum still -6% โ Continue observing Minute 12: Momentum -1.8% โ Still volatile Minute 18: Momentum -0.4% โ Neutral (streak = 1) Minute 19: Momentum -0.3% โ Neutral (streak = 2) Minute 19: RELEASE
Order fires near exhaustion instead of mid-crash.
๐ What Happens If Volatility Returns?
If during observation:
- A volatile reading appears again
- Explosive threshold is breached
Then:
- Neutral streak resets
- Observation continues
This avoids premature execution.
๐ง Why This Lifecycle Matters
The observation lifecycle:
- Converts DCA from reactive to adaptive
- Filters panic-driven moves
- Waits for statistical edge to improve
- Preserves capital during extreme events
Without this lifecycle:
- All DCA levels can trigger in rapid succession
- Exposure grows aggressively during instability
With this lifecycle:
- Orders are timed with momentum exhaustion
- Tail-risk stacking is reduced
โ๏ธ What the Lifecycle Does NOT Change
It does not:
- Modify deviation logic
- Change order size
- Alter multipliers
- Affect SL/TP
- Skip DCA entirely
It only changes when execution happens.
๐ Summary
The DCA observation lifecycle is:
A structured monitoring phase between deviation trigger and order placement.
It ensures that once activated, the system:
- Watches volatility
- Waits for stabilization
- Confirms neutralization or reversal
- Then executes at a safer moment
- Or force-releases after timeout
In simple terms:
Traditional DCA reacts instantly. Observation-based DCA waits intelligently.
If you'd like, I can also generate a state-machine diagram explanation (Idle โ Triggered โ Held โ Watching โ Released โ Completed) for technical documentation.