Decision Architecture
How trading systems form decisions, where assumptions fail, and how risk and execution behave under real market conditions.
Alistair Beaumont
Quant Systems & Trading Architecture
Designing robust systems that form decisions, manage risk, and perform under real market conditions.
Featured product
ABQ Forensics
Post-trade investigation, root-cause attribution, and tamper-evident evidence for algorithmic trading.
Featured strategy
Systematic Strategy
A proprietary, Python-based trend-following system researched in QuantConnect across SPY and QQQ.
How trading systems form decisions, where assumptions fail, and how risk and execution behave under real market conditions.
Construction of risk logic, capital allocation, and volatility-aware decision layers that govern system behavior.
Defining when systems trade, pause, scale, or stop — under stress, regime shifts, and execution constraints.
I work with traders, funds, and founders already deploying real capital — where system behavior matters more than ideas.
If the question is still what to trade, we are likely not a fit.
I start by defining how systems are allowed to fail — and where they must never fail. Then I define how risk, capital, and execution must behave without discretion.
If risk is wrong, signal quality is irrelevant.
Most systems are not designed for change.
A system that cannot survive cannot compound.
Participation is optional; preservation is not.
This is not strategy generation. This is system architecture.
Problem: Live performance collapsed despite clean backtests.
Intervention: Position risk and exit policy were rebuilt as volatility-aware constraints.
Result — lower drawdown severity and no regime-specific breakpoints during volatility spikes.
Problem: More strategies increased portfolio risk faster than returns.
Intervention: Regime overlap and tail co-movement were mapped; allocation was rebuilt as a regime-budgeted risk policy.
Result — lower realized volatility and fewer clustered drawdowns.
Problem: Strategy edge decayed after deployment due to slippage and execution friction.
Intervention: Execution assumptions and exit constraints were rebuilt around latency, liquidity, and fill uncertainty.
Result — observed performance converged with realistic execution expectations.