# Risk Management

#### Risk is embedded, not appended

UNIKO’s risk philosophy is that risk controls must be integrated into the operating structure:

·      All strategies operate under predefined exposure boundaries.

·      Execution paths and scaling operate under governance rules.

·      Monitoring detects deterioration during operation, not only after losses.

#### Risk control domains

**Position and exposure control**

Controls may include:

·      Max position size per asset

·      Max inventory skew (deviation from target inventory)

·      Max concentration per venue

·      Max notional per execution window

**Liquidity risk control**

Controls may include:

·      Slippage caps per trade

·      Price impact estimates (DEX)

·      Depth-aware sizing on CEX order books

·      Illiquidity detection triggers for throttle/pause

**Execution risk control**

Controls may include:

·      Failure rate detection

·      Order rejection thresholds

·      Latency spike detection

·      Partial fill deterioration rules

**System-level protection**

Controls may include:

·      Kill-switch triggers

·      Automatic throttling based on drawdown

·      Venue health gates

·      Data integrity halts

#### Stress scenario response playbooks

**Scenario: sudden volatility spike**

·      Observed risk: adverse selection increases; slippage widens; fills degrade

·      System response: widen quoting bands; reduce size; increase spread thresholds; throttle execution

**Scenario: venue degradation (CEX)**

·      Observed risk: reject rates rise; latency spikes; order book becomes unstable

·      System response: switch venues; reduce order rate; cancel open orders; pause venue if needed

**Scenario: DEX liquidity drop**

·      Observed risk: pool imbalance increases; price impact becomes steep

·      System response: reduce swap size; pause swaps; route via alternative pools; rely on CEX execution until depth returns

**Scenario: data feed integrity issues**

·      Observed risk: stale or inconsistent market data causes unsafe execution decisions

·      System response: halt execution; failover data feed; require health checks before resuming

#### Circuit breakers (illustrative examples)

These are illustrative only and should be published as final parameters only after production validation.

<table data-header-hidden><thead><tr><th valign="bottom"></th><th valign="bottom"></th><th valign="bottom"></th></tr></thead><tbody><tr><td valign="bottom">Circuit breaker</td><td valign="bottom">Illustrative trigger</td><td valign="bottom">Illustrative response</td></tr><tr><td valign="bottom">Slippage guard</td><td valign="bottom">Slippage > S% repeatedly within window</td><td valign="bottom">Reduce size; reroute; pause pair</td></tr><tr><td valign="bottom">Failure burst</td><td valign="bottom">> N rejects/failures in M minutes</td><td valign="bottom">Cancel orders; halt execution; alert</td></tr><tr><td valign="bottom">Inventory skew cap</td><td valign="bottom">Inventory deviation > I%</td><td valign="bottom">Rebalance; reduce one-sided quoting</td></tr><tr><td valign="bottom">Drawdown throttle</td><td valign="bottom">Rolling PnL &#x3C; -D threshold</td><td valign="bottom">Reduce risk; move to defensive mode</td></tr><tr><td valign="bottom">Data integrity halt</td><td valign="bottom">Feed stale beyond T seconds</td><td valign="bottom">Pause; failover; alert</td></tr></tbody></table>

Illustrative parameter ranges (non-binding)

<table data-header-hidden><thead><tr><th valign="bottom"></th><th valign="bottom"></th></tr></thead><tbody><tr><td valign="bottom">Parameter</td><td valign="bottom">Illustrative range</td></tr><tr><td valign="bottom">Slippage cap (stable markets)</td><td valign="bottom">0.10%–0.30%</td></tr><tr><td valign="bottom">Slippage cap (volatile markets)</td><td valign="bottom">0.30%–0.80%</td></tr><tr><td valign="bottom">Inventory deviation cap</td><td valign="bottom">5%–25% of target</td></tr><tr><td valign="bottom">Failure burst threshold</td><td valign="bottom">3–30 failures in 1–10 minutes</td></tr><tr><td valign="bottom">Drawdown throttle trigger</td><td valign="bottom">1%–10% rolling drawdown</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://uniko.gitbook.io/uniko-whitepaper/risk-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
