SERVICES / QUANT
EVIDENCED BY THE ARCHIVE
Multi-strategy architectures where entries, exits and risk are code, not discretion.
WHO THIS IS FOR — Builders who want execution, risk and costs modelled in code — with paper execution as the default and live capital deliberately out of scope.
THE PROBLEM IT ADDRESSES
- Discretionary execution that cannot be audited, replayed or reviewed after the fact.
- Risk controls that exist as conventions instead of structural invariants enforced before an order exists.
- Costs that are assumed rather than modelled, so paper results evaporate on contact with fees and slippage.
EXPECTED DELIVERABLES
- A signal-contract architecture separating data, signal, risk and execution concerns.
- Structural risk gates: position sizing, R:R floors, cost-budget filters — enforced in code.
- Deterministic backtesting with explicit fees and slippage, plus paper execution as the honest default.
OUT OF SCOPE
- Connection to a live brokerage account with real capital.
- Proprietary strategy alpha — the architecture is yours; the signals are the question we research together.
- Custody, funding or account operations of any kind.
TECHNICAL APPROACH
HOW THE WORK IS DONE
Rule-based multi-strategy trading architectures where entries, exits and sizing are code, not discretion.
SCHEMATIC · SOFTWARE DEVELOPMENT
METHODS
Multi-strategy engines · Signal contracts · Paper execution
EVIDENCE
apex-quant-engine and automated-trading-os implement multi-strategy engines, signal contracts and paper execution as code.
RELEVANT PROJECT EXAMPLES
WORK THAT PROVES IT
RELATED RESEARCH
THE WRITTEN RECORD
LIMITATIONS
SCOPE & LIMITS
- All performance evidence is BACKTEST or PAPER labelled; nothing here is a live trading record.
- Structural controls reduce specific failure modes; they do not make a strategy profitable.
- Regime dependence is a real limitation and is documented rather than smoothed away.
WORKING PROCESS
HOW THIS ENGAGEMENT RUNS
- 01SIGNAL CONTRACT
- 02STRUCTURAL RISK GATES
- 03EXPLICIT COST MODEL
- 04PAPER EXECUTION AS THE DEFAULT
Each stage produces something checkable. The full process, with what every stage produces across all work, lives on the process page. Every engagement starts the same way: describe the problem, the data, and the evidence that would count as success.