Skip to content
Trust and methodology

Risk methodology

The limit is written first. The position is whatever survives it.

Risk management here is not a dashboard showing exposure after the fact. It is a condition every order passes before it leaves. What breaches the limit is not sent.

The limit before the position

No order without a limit written beforehand. The maximum acceptable loss is set first and the position size derived from it, not the other way round. An order that carries no limit is refused, and that is a structural refusal rather than a warning.

A binding risk budget

Exposure, concentration and drawdown are numeric limits at the system level, not guidance for the user. Approaching a limit narrows the permitted size before it is reached; breaching one stops execution.

The halt works from our side

An emergency halt stops orders being sent, and depends on neither a user's response nor a notification arriving. A control that requires somebody to notice it is not a control.

Every refusal leaves a record

No order is refused silently. The order, the limit it breached, the inputs at the time of the check and the timestamp are all recorded. The refusal log is part of the product, not a side effect of it.

Periodic review

Limits are reviewed every ninety days and on any material change in market behaviour. A limit that is never revisited becomes an inherited number rather than a decision.

Trading and investing involve risk and may result in partial or total capital loss. Historical examples or simulations do not guarantee future outcomes.

This section does not provide personal financial advice. Information is general and methodological, and requires the user's own judgement and independent review.