Your first steps in Aurora
Open Aurora using the link below and describe one rule. On the returned card, select View Portfolio to inspect the definition. Ask Aurora to propose the test dates, capital and benchmark, then approve the historical run after checking those values. You can also use the portfolio Backtest control and select Run Backtest after setting its dates.
| Asset | SPY |
| Entry | A stated indicator condition, with its lookback period |
| Sizing | A stated dollar amount or allocation with a maximum exposure |
| Exit | A stated sell condition and which position it closes |
| Timing | Daily evaluation with explicit test dates |
No matching rows. Clear the filter to see all records.
Describe the rule, then inspect it
Open Aurora in NexusTrade and explain the universe, entry condition, sizing and exit condition in plain language. Aurora can produce the portfolio definition, but the review step is where you confirm that the stored rule means what you intended.
Start with a simple, bounded candidate. A request such as buy good stocks is not an executable rule; a specific condition, asset and sizing decision is.
Use a concrete first request
Choose your test dates, capital and appropriate benchmark before submitting. The prompt below is example research configuration, not a trade recommendation or a reported result.
Create a daily SPY candidate with explicit entry, sizing and exit rules. Show me the complete definition before running anything. Propose one fixed historical test period and a buy-and-hold SPY comparison. Wait for my approval to submit the backtest. Do not deploy it.Inspect more than the return
After the job finishes, read its warnings, drawdown, activity and benchmark comparison. Ask whether the strategy traded enough to address your question and whether exposure was concentrated. Missing data and model assumptions remain part of the result.
A high historical return after many attempted variants does not by itself establish a robust candidate. Record the selected rule and then test a period you did not use to choose it.
Decide whether to keep researching
Save the accepted definition and operation identity. Change one hypothesis deliberately rather than asking for a prettier result. If the rule advances, begin a separately reviewed paper observation with simulated money.
Aurora stores explicit strategy rules and uses the same engine as the SDK. Review the proposed run in Aurora before submitting it; opening this guide does not start a backtest or deployment.