Follow the critical EDGE journey: Evaluate the idea, Design explicit rules, Generate validated NinjaScript, compile and backtest in NinjaTrader Strategy Analyzer, then Evolve from the evidence. Explore the demos, evidence packets, benchmark scope, and limitations together.
NQ / ES
primary futures markets
60
benchmark specifications
2
bounded repair passes
Pending
native compile-rate claim
The headline workflow
A narrated founder demonstration of an NQ scalping concept moving from an Evaluation Brief to a Strategy Specification, NinjaScript, NinjaTrader Strategy Analyzer, and an evidence-led Evolve review.
A connected project, explicit NQ rules, generated NinjaScript, the independent NinjaTrader handoff, Strategy Analyzer use, and backtest evidence returned to Evolve.
The walkthrough is not a compilation-rate statistic, customer outcome, verified performance claim, signal, recommendation, or guarantee that historical results will repeat.
One critical customer journey
The product is organized around the first successful backtest and the next evidence-led iteration—not a collection of disconnected assistants.
Step 1
Turn an NQ or ES concept into a bounded research brief with assumptions, constraints, and open decisions.
Step 2
Define explicit entries, exits, risk controls, session logic, and test conditions before generating code.
Step 3
Generate NinjaScript from the approved specification, validate known failure modes, repair, and revalidate.
Step 4
Compile and test independently in NinjaTrader Strategy Analyzer with retained settings and assumptions.
Step 5
Return the report, diagnose the evidence, and choose a controlled experiment, additional validation, or a justified no-change decision.
Claims matched to evidence
The primary proof path follows an NQ futures idea through structured design, NinjaScript generation, independent NinjaTrader testing, and evidence-led refinement. Every claim below states its boundary.
Primary product proof · NinjaTrader 8
Go beyond the walkthrough: inspect the connected Evaluate and Design context, generated NinjaScript handoff, Strategy Analyzer step, returned Evolve evidence, and the limits of the validation controls.
Open the NinjaTrader evidence packetSecondary platform proof · TradingView
TradingView remains supported. Its dedicated packet preserves three downloadable Pine files, SHA-256 checksums, backtest assumptions, source diffs, and unresolved limitations. This is founder-created cross-platform evidence, not a customer result.
Inspect the TradingView packetGenerate reliability
The internal corpus currently contains 60 structured strategy requests: 30 for NQ and 30 for ES. Prompt, model, validator, and repair changes are expected to run against the same corpus so regressions remain visible.
EMA crossover and multi-condition entries
RSI, ATR, breakout, and time-window filters
Long-only, short-only, and asymmetric logic
Fixed, trailing, and volatility-scaled exits
Daily loss limits and multiple contracts
NQ and ES across 1, 5, 15, and 30-minute charts
Current boundary: static corpus integrity and non-native application checks pass in application QA. The native benchmark check remains blocked by missing compiler results. Requires retained Windows/NinjaTrader results from documented manual testing or a verified compiler worker. No public compile-success rate is claimed.
Evidence register
| Evidence | Status | What the status means |
|---|---|---|
| Structured EDGE project workflow | Implemented | Evaluate, Design, Generate, Backtest handoff, and Evolve remain connected inside one saved Strategy Project. |
| NQ NinjaTrader workflow | Demonstrated | The narrated founder walkthrough shows an NQ idea becoming NinjaScript, moving into NinjaTrader Strategy Analyzer, and returning for refinement. |
| NQ/ES Generate benchmark coverage | Corpus structure verified | A permanent 60-case corpus covers 30 NQ and 30 ES specifications across intervals, directionality, filters, and risk controls. |
| Deterministic NinjaScript preflight | Implemented | Generated code is checked for required structure, identifier and API risks, unsupported constructs, order conflicts, and incomplete output before delivery. |
| Native NinjaTrader compilation rate | Not yet published | Requires retained Windows/NinjaTrader results from documented manual testing or a verified compiler worker. A public rate must state the tested sample, runtime, and failures. |
| Customer performance outcomes | No claim | Founder demonstrations and hypothetical backtests are not customer results, financial advice, or evidence of future profitability. |
The operating standard
The platform is a research workspace—not a signal service, broker, autonomous trading system, or guarantee of profitability. The trader owns the hypothesis, test settings, risk decisions, and deployment.
Secondary platform evidence
These BTC demonstrations remain available as cross-platform evidence. They no longer define the product’s headline promise, primary customer, or primary acquisition journey.
Secondary workflow · TradingView · Pine Script
See the secondary TradingView workflow as a Bitcoin concept moves through evaluation, rule design, Pine Script generation, independent backtesting, and refinement.
Watch with transcript
Secondary workflow · TradingView · Pine Script
Watch the complete secondary-platform case study: Bitcoin rules, generated Pine Script, TradingView backtests, and evidence-led revisions through the EDGE Method.
Watch with transcriptKeep testing after the video
Compile, configure Strategy Analyzer, retain settings, and return usable evidence.
Read the primary guideReview direction, time, drawdown, outlier, and cost sensitivity before changing a rule.
Analyze the evidencePrefer one-variable hypotheses, stable regions, and explicit keep-or-reject decisions.
Read the optimization guideSeparate development from evaluation and document what survives unseen periods.
Read the validation guideNeed the secondary platform workflow? Read the TradingView backtesting guide.
Start with Evaluate, approve the Design, Generate NinjaScript, run the independent NinjaTrader backtest, and keep every result and experiment connected to the project.
Educational strategy-development software. No signals, brokerage, personalized financial advice, or performance guarantees.