Quant Risk & Trading Safety Engineering
The controls that decide how bad a bad day gets: position sizing, exposure and drawdown limits, daily loss stops, circuit breakers, stale-data detection and restart recovery — enforced in the execution path where they cannot be bypassed.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
What's covered
- Position sizing methodology and its assumptions, stated openly
- Exposure limits by instrument, sector, currency and total notional
- Drawdown controls: per-day, per-week and peak-to-trough
- Daily loss stop and the halt authority behind it
- Volatility-aware sizing and regime-change handling
- Circuit breakers and automated kill-switch triggers
- Stale-data, disconnect and clock-skew detection
- Restart recovery: reconciling positions before resuming trading
What you receive
- Risk control layer integrated into the execution path
- Documented limit set with the reasoning behind every number
- Kill-switch design with trigger conditions and manual override
- Stale-data and connectivity failure handling
- Restart and recovery procedure, tested
- Risk monitoring dashboard and alerting
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Written scope firstAdvisory work runs to a written scope agreed before it starts, so what you receive is what was agreed.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Risk controls limit exposure; they cannot prevent loss and we never claim they can
- Gap moves, halts and liquidity events can exceed any configured limit
- No investment advice, position recommendations or return targets
- Limits are yours to set — we engineer their enforcement and challenge them
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Can a kill switch guarantee we do not blow up?
- No. A kill switch stops new risk being taken; it cannot exit positions into a market with no bids, and it cannot undo a gap through your stop. It converts an unbounded failure into a bounded one, which is worth a great deal and is not the same as safety.
- Where should risk checks live?
- In the execution path, so nothing can place an order without passing them. Risk logic that lives in the strategy is advisory: the day a second strategy, a manual override or a retry path bypasses it is the day it was never a control.
- What is the most commonly missing control?
- Stale-data detection. Systems reliably handle a feed that disconnects and reliably mishandle one that keeps delivering the same price. Trading confidently on a frozen quote has emptied more accounts than most strategy errors.
Related services
Algorithmic Systems
Algorithmic Trading System Engineering
Trading infrastructure engineered like safety-critical software: a data pipeline you can trust, a strategy engine you can reason about, an execution path with risk gates in front of it, and a kill switch that works when everything else does not.
Algorithmic Systems
Broker / Exchange Execution & OMS Engineering
The order path, built to survive reality: broker and exchange adapters, an explicit order state machine, retries that do not duplicate, reconciliation that catches drift, and the latency observability to know which of those is failing.
Algorithmic Systems
Strategy Backtesting & Research Validation
An independent examination of whether a backtest demonstrates anything — realistic costs, walk-forward and out-of-sample testing, and a deliberate hunt for the leakage, survivorship and overfitting that make most impressive equity curves meaningless.