The agent team and pipeline

Six specialised agents pass each strategy along a fixed sequence of stages with checks between them.

The six agents

The Research Lead writes hypotheses. The Strategy Developer codes them as NautilusTrader strategies. The QA Agent reviews the code for logic, signal polarity, edge cases and fee viability. The Strategy Analyst reads backtest and optimisation results and decides what happens next. The Risk Officer audits a promoted strategy's safety. The Portfolio Manager decides promotion and retirement across the whole book.

Stages in order

A run moves through coding, verifying, backtesting, backtest review, optimising and analysing. From analysing it can iterate back to coding, be abandoned, or move on to risk review, promotion and paper trading. Later stages are processed first so that verification and backtesting never starve behind a queue of new code.

Verification before any backtest

Code passes four layers before it touches market data: static analysis of the source, synthetic scenario tests with fabricated funding, open-interest and liquidation data, a short sandbox backtest on real bars that must produce at least one trade, and a QA review of the logic and fee viability. A failure returns the run to the developer with the finding.

The two analyst decisions

After the first backtest the analyst decides optimise, iterate or abandon, so hours of optimisation are only spent on ideas with a real signal. After optimisation the analyst decides promote, iterate or abandon with the out-of-sample and holdout evidence in hand. Every decision is stored with its reasoning on the strategy page.

Iteration limits and abandonment

A strategy is abandoned when its average trade return is below trading costs, when its out-of-sample performance fails, when it repeatedly fails verification, or when the analyst sees no path to viability. The reason is recorded and feeds back into the research agent so the same dead end is not repeated.

Platform runs and your runs

The platform runs its own research continuously; your workspace runs alongside it with reserved capacity and higher priority, so your idea is not queued behind platform work. You can pause, resume or stop your own runs at any time from the strategy page.