ALAMO Hotfix12 — Stagger Flow

Current vs Proposed behavior when Con1 breaks during high DD

Current State Machine

Ctrl/Cmd + wheel to zoom. Drag to pan.

Loading...
Problem: When L1 captures snapshot but Con1 breaks (any position profitable), state resets to STANDBY. Snapshot is cleared. DD can continue rising to 20%+ while ALAMO "sleeps" waiting to restart from L1.

Proposed Stagger Flow

Ctrl/Cmd + wheel to zoom. Drag to pan.

Loading...
Solution: When L1 can't fire (Con1 broken) but DD is high, keep snapshot and advance nextLnIdx = 2. Transition to S3_MONITOR where L2 monitors independently. If DD hits 20% + Con1 OK, L2 fires using L1's snapshot.
Key Insight
The critical change is in S1_MONITOR: instead of returning to STANDBY when Con1 breaks, we escalate to S3_MONITOR and let the next level monitor. This creates a "stagger" pattern where each Ln monitors independently and can fire without Ln-1 actually firing first.

SS Spec: "Alamo L1 da co position, da co snapshot, nhung khong fire vi khong hop dieu kien. Thi Alamo L2 van se monitor doc lap va dung du lieu tu L1 de track log kem vi tri."
Open Questions for SS
  1. Snapshot inheritance: When L1 staggers, does L2 use L1's snapshot or capture a fresh one?
  2. Ln recovery: If L1 staggers then Con1 becomes valid again, can L1 still fire or is it skipped?
  3. Index after stagger-fire: When L2 fires from L1 stagger, what's nextLnIdx? (3 or 2?)