Confidential overview for fund diligence

NEO Orderflow Engine / NEO Stock Engine

Two systematic execution engines presented from source-of-truth backtests: the Orderflow replay dashboard with Point Zero B1000-B1700 systems, and the published NEO Stock PnL dashboard. The fund gets performance, calendar behavior and full trade-level review without the proprietary signal recipe.

Active view-
System-
Markets-
Trades-
Window-

What the fund should understand before a test.

The page is built as a diligence view: source dashboards first, then summarized performance, calendar distribution and complete trade logs. Exact signal weights, thresholds and arbitration logic remain withheld.

Orderflow B1200 PnL--
Orderflow B1200 PF--
Stock 100K PnL--
Stock 100K PF--
Orderflow truth source

Replay dashboard: Point Zero B-Ladder

The Orderflow section uses the same replay-data source as the live replay page, covering PZ B1000, B1200, B1400 and B1700 across MNQ, MGC, MCL, MES and M2K.

Dashboard access is withheld for this diligence preview.

Stock truth source

Published uncapped stock PnL page

The Stock section uses the published NEO stock page plus the selected trade CSVs behind that dashboard. Headline PnL is shown for the 100K account allocation.

Dashboard access is withheld for this diligence preview.

Point Zero B1000-B1700 replay results.

Select a B-system to update the metrics, symbol contribution, calendar and trade table. The data is loaded from the Orderflow replay dashboard source.

System selector

Net PnL--
Trades-Completed trades
Profit Factor-Gross profit / loss
Win Rate--
Max DD-Closed-trade equity
Period--

B-System Comparison

Source: replay-data.json
SystemTradesPnLMax DDPFWinDays

Selected System by Symbol

-
SymbolTradesPnLMax DDPFWin

Orderflow Calendar

-

Orderflow Monthly PnL

Selected B-system
MonthDaysTradesPnLWinsLosses

Complete Orderflow Trade Overview

-
DateSymbolDirLotsSetupScoreEntryExitDurPtsPnLExit reason

Published stock PnL, allocation and full trade view.

Stock results are the current published uncapped portfolio set. Headline KPIs use the 100K account allocation; the complete trade log below remains the selected system CSV audit view.

Net PnL-100K account allocation
Trades--
Profit Factor-Gross profit / loss
Win Rate-Selected trades
Max DD-Daily DD -
Period--

Selected Stock Systems

100-share baseline
SymbolFamilyTradesPnLPFMax daily DDOverall DD

1% Daily-DD Account Allocation

No share cap, published sheet
ModeAccountPnLMax Daily DDPFTradesMax concurrent

Stock Calendar

100-share selected trades

Stock Monthly PnL

100-share selected trades
MonthDaysTradesPnLWinsLosses

Complete Stock Trade Overview

-
DateSymbolFamilyDirSetupScoreEntryExitBarsRPnL @100Exit reason

Enough detail for diligence, not enough to clone.

The fund can review trade distributions, timing, exits, symbol concentration and drawdown behavior. The internal signal stack, feature thresholds and arbitration logic are intentionally not disclosed.

Inputs used

Orderflow bars, volume behavior, market context, value-area/profile levels and multi-timeframe structure. Stock data uses aggregated bid/ask volumetric bars, not full Level II depth.

Decision layer

Candidate setups are scored, filtered and handled by system families. The overview exposes setup names and outcomes, not the exact trigger formulas.

Risk layer

Replay exits include stop checks, partial/management behavior and dynamic exit reasons. Stock allocation is constrained by a hard daily drawdown rule.

A controlled test before scaling.

The right next step is a shadow or small-capital evaluation where fills, rejected trades, latency, slippage and drawdown behavior are measured against this backtest story.

Suggested structure

  • 2 to 4 weeks shadow or controlled paper/live test.
  • Daily reconciliation against engine decisions and modeled exits.
  • Separate review for futures and equities.
  • Explicit slippage, fee and rejection log.

Decision criteria

  • Does live/paper behavior match replay within acceptable tolerance?
  • Is the drawdown shape acceptable for the mandate?
  • Do concurrent trade counts and gross exposure fit infrastructure?
  • Which systems and markets should be enabled, disabled or capped?