TL;DR
Durable performance starts with controlled downside. Define hard limits before execution and enforce them consistently.
Clear explanation
Crypto moves faster than discretionary reaction speed, so risk rules must be explicit and pre-committed.
Core controls include per-trade risk caps, daily stop limits, portfolio heat limits, and correlation checks.
Professional practice separates signal quality from risk permissions, especially in high-entropy regimes.
Technical example: portfolio heat control
A portfolio limits total open risk to 2.5% of NAV; one proposed correlated position is rejected.
- 01Compute trade risk from entry, stop, and size.
- 02Aggregate risk across correlated positions.
- 03Reject or resize positions above heat cap.
- 04Log decision with score and SNAP context.
ASCII model
Signal quality -> Risk gate -> Position sizing -> Heat check -> ExecutionRisk controls by layer
| Layer | Control | Failure prevented |
|---|---|---|
| Trade | Fixed risk per position | Single-trade outsized loss |
| Book | Heat + correlation limits | Clustered drawdown |
| Process | Daily stop + review | Policy drift |
Related pages
- Market Status framework →Align exposure with CLEAR/TENSE/NO-TRADE states.
- Verify historical context →Audit whether losses were variance or process violation.
- Market Score concept note →Future methodology note only. It is not a live SignalX field.
- How to interpret score concepts →Review how a future composite score could be turned into formal control actions.
FAQ
Most common crypto risk mistake?
Oversizing during unstable regimes and ignoring correlation concentration.
Should stops always be static?
Not usually. Volatility-aware stops are generally more robust in crypto.
How should policy be documented?
Use a written rulebook with limits, escalation triggers, and review cadence.