NQ idea to NinjaScript: the evidence packet
This packet separates what the founder demonstration visibly shows, what the application validates deterministically, and what still requires retained native NinjaTrader compiler evidence.
What the walkthrough demonstrates
- A specific NQ concept enters a structured EDGE project.
- Evaluate context is carried into a reviewable Strategy Specification.
- Generate produces NinjaScript for independent platform use.
- The script moves into NinjaTrader Strategy Analyzer.
- Backtest evidence returns to Evolve for focused diagnosis.
What it does not prove
- A statistically measured native compilation rate.
- A byte-for-byte link between public video frames and a retained source artifact.
- After-cost, forward, paper, or live profitability.
- That a generated strategy is appropriate for another trader.
- That historical or simulated results will repeat.
The critical customer journey
One connected path to the first successful backtest
The proof target is not “AI wrote some code.” It is whether a trader can move from an owned hypothesis to an independently tested strategy, understand the evidence, and make a deliberate next decision.
Evaluate the NQ idea
State the market, chart interval, objective, assumptions, constraints, and unresolved choices before rules are invented.
Design explicit behavior
Convert the approved idea into entries, exits, filters, sizing, session handling, and risk controls that can be reviewed before code.
Generate and validate NinjaScript
Build a complete strategy from structured Design context, run deterministic checks, repair identified failures, and preserve the delivered artifact.
Compile and backtest in NinjaTrader
The trader independently compiles the script and runs Strategy Analyzer with retained instrument, interval, date, cost, and session settings.
Evolve from evidence
Return the report to the same project, diagnose the evidence, and choose a controlled experiment, additional validation, or a justified no-change decision.
Generate validation
Structured generation with deterministic gates
The generation path uses the approved Design as its contract. The first result is inspected against NinjaScript-specific rules; identified failures feed a bounded repair pass, and the repaired result is validated again before delivery.
Required NinjaTrader namespaces and a complete Strategy class
OnStateChange and OnBarUpdate lifecycle structure
State initialization and BarsRequiredToTrade safeguards
Indicator constructor and supported API usage
Undefined identifiers and unsupported properties
Order-method validity and duplicate/conflicting order risk
Time-window, session-boundary, and daily-reset handling
Prohibited indicators and obvious look-ahead patterns
Incomplete or truncated output
Repair revalidation before an artifact can be delivered
Important distinction: deterministic preflight catches known structural and API risks, but it is not NinjaTrader itself. Native compilation remains a separate gate. The production path is designed to fail closed when a configured native compiler cannot verify an artifact.
Permanent regression suite
60 NQ and ES strategy specifications
The corpus is intentionally broader than the public demo. Its purpose is to make reliability measurable across common futures-strategy patterns instead of optimizing for one showcase request.
| Coverage area | Included cases |
|---|---|
| Markets | 30 NQ specifications and 30 ES specifications |
| Intervals | 1, 5, 15, and 30-minute charts |
| Direction | Long-only, short-only, symmetric, and asymmetric logic |
| Entries | Crossovers, breakouts, RSI filters, and multi-condition setups |
| Risk | ATR stops, targets, trailing logic, daily loss limits, and multiple contracts |
| Regression goal | Expose prompt, model, validator, or repair changes that improve one pattern while breaking another |
60
total specifications
30
NQ specifications
30
ES specifications
The next evidence required before a compilation claim
Configure the external Windows worker with NinjaTrader installed, run every applicable corpus artifact through native compilation, retain the compiler result and source fingerprint, measure first-pass and final-pass outcomes separately, and publish the denominator with the rate. Until then, the public status remains “native benchmark pending.”
Available now
Structured generation, deterministic validation, bounded repair, release QA, saved artifacts, and the NQ workflow demonstration.
Pending infrastructure
Retained native NinjaTrader compiler evidence across the benchmark corpus and a defensible public compilation-success statistic.
Build the first version inside a saved Strategy Project
Start with your own NQ or ES idea. The Strategic Edge AI structures the research workflow; you retain control of the hypothesis, source review, NinjaTrader settings, risk assumptions, and any decision to deploy.
Educational strategy-development software. No signals, brokerage, personalized financial advice, or performance guarantees.