Risk Protocols & The 24-Hour Oath
"Discipline enforced by algorithm, not willpower."
The Risk Protocol system turns your risk parameters into immutable rules that cannot be changed in moments of emotional trading. When you set a risk limit, you're making an oath — one that the system enforces for a minimum of 24 hours.
The Problem
Every experienced operator knows the pattern:
- Set Max Daily Loss to $500
- Hit the limit after a bad session
- Emotion overrides logic — increase to $1,000 to "recover"
- Result: $2,000 loss instead of $500
🚨 The Pain Point
Self-imposed limits fail because the person imposing them is the same person who wants to override them. Alpha Draconis separates the decision-maker (calm you) from the executor (emotional you) using a 24-hour time lock.
How Time-Lock Works
Setting Parameters
Configure your risk limits via Dashboard → Risk Configuration:
| Parameter | Description | Example | |-----------|-------------|---------| | Max Daily Loss | Absolute dollar loss ceiling per day | $500 | | Hard Equity Stop | Emergency equity floor | $8,000 | | Max Position Size | Largest single trade | 0.50 lots | | Max Open Positions | Concurrent position limit | 3 |
The 24-Hour Rule
Once saved, each parameter enters a locked state:
| Action | Allowed? | When? | |--------|----------|-------| | Tighten (reduce risk) | ✅ Always | Immediate | | Loosen (increase risk) | ❌ Blocked | After 24 hours | | Same value | ✅ No change | Always |
ℹ️ Example
You set Max Daily Loss = $500 at 10:00 AM Monday.
- At 2:00 PM Monday, you can tighten to $300 → ✅ Immediate
- At 2:00 PM Monday, you try to loosen to $800 → ❌ Locked until 10:00 AM Tuesday
- At 10:00 AM Tuesday, you can change to $800 → ✅ Lock expired
Lock Visualization
The Dashboard displays a countdown timer next to each locked parameter:
Max Daily Loss: $500
🔒 Locked — Loosening available in 16h 24m
(Tightening: always available)
Cloud Synchronization
Risk parameters are stored in the cloud and synchronized to all connected systems:
Dashboard → Save Config → Cloud Database
↓ ↓
Time-Lock Enforced Arsenal EA receives via heartbeat
↓
Risk Guardian enforces locally
Both the cloud and the Algorithm enforce limits independently. Even if the cloud connection drops, Arsenal uses the last-known configuration. When connection resumes, the most restrictive values prevail.
🐉 Dual Enforcement
Cloud says Max Loss = $500. Local says Max Loss = $300 (tightened while offline). The system enforces $300 — the stricter value always wins. This is Zero-Trust risk management.
Risk Levels
The system supports three escalation levels:
Level 1: Warning
- Daily loss reaches 70% of Max Daily Loss
- Alert sent via Telegram
- Algorithm continues trading
Level 2: Restriction
- Daily loss reaches 100% of Max Daily Loss
- New positions blocked
- Existing positions monitored (not closed)
Level 3: Hard Stop
- Equity drops below Hard Equity Stop
- All positions closed immediately
- Algorithm enters lockdown until next trading day
- Dashboard, Telegram, and Sentry alerts fired
🚨 Hard Stop is Absolute
When Level 3 triggers, MT5 goes into lockdown. Only the Dashboard admin can unlock early. No amount of clicking in MT5 will resume trading. This is the system working as designed.
Configuration Best Practices
| Operator Level | Recommended Max Daily Loss | Hard Equity Stop | |----------------|---------------------------|------------------| | Conservative | 1-2% of account | Account - 5% | | Moderate | 2-3% of account | Account - 8% | | Aggressive | 3-5% of account | Account - 10% |
💡 Start Conservative
Begin with 1% Max Daily Loss. After 30 consecutive days without hitting the limit, consider adjusting. The 24-Hour Oath ensures any adjustment is deliberate, not impulsive.
Next Steps
- 📖 Arsenal Core — How Risk Guardian enforces locally
- 📖 Hydra Network — Cross-exchange risk enforcement
- 📖 Sentinel Node — Cloud monitoring infrastructure