Overview

Getting started

Use simulation and a supported live market-data connection before enabling automated orders. Xtrend has distinct layers: NinjaTrader detects and routes; the optional desktop Control Center exposes a localhost service; BookMap/Footprint/VWAP dependencies supply evidence. The desktop app does not load NinjaTrader assemblies or command the strategy.

1. Import the vendor’s complete NinjaTrader export, including every required custom indicator. Compile in NinjaScript Editor. If types such as XtrendBookMap are missing, stop and obtain the complete dependency export.
2. Open a chart for the intended instrument and connect a feed that supplies the data required by your selected features. Depth-driven features need valid bid/ask depth; a bar-only connection is not equivalent.
3. Add the required indicators first, then add XtrendGoldEditionPlus as a strategy. Use a Simulation account for first use.
4. Confirm the account, quantity, session/risk limits, order method, and Combine Mode. Apply the strategy only after reviewing the NinjaTrader log/output.
5. For optional Flow AI, start the licensed desktop application. Its healthy state can be checked at the local service; an absent validated model is an expected state, not evidence of a working confirmation gate.

Exact menu clicks and all indicator dialogs require screenshot/runtime verification; source code alone cannot establish a customer’s NinjaTrader build or installed dependency set.

Every Strategy Setting

BookMap detector parameters — interpretation guide

Reference values above originate from the supplied source-audit parameter matrix, not from a verified active customer template. They should not be copied blindly as recommended settings.

Complete strategy parameter catalog

How to read this catalog

AI entry confirmation —

L2 Micro —

L2 learning and research —, research partials

Context and ledger

BookMap integration, diagnostics, and legacy ML

The remaining exposed strategy controls are source-owned integration properties in the strategy build, . Full source-visible names, defaults, and status are preserved in the coverage report. High-impact controls: UseBMLiquidityWall=true, SpoofingReversal=false, WallEngineMode=Legacy, BMExecutionEngine=Legacy, BMFastLimitMode=Marketable, BMFastRequireReference=true, and WallRequireFreshAtEntry=true. Auto-adjust defaults: disabled; Balanced; lookback 120, minimum 30, update 5 seconds, strength 60%, smoothing 25%, maximum change 50%, freeze on active signal/position true.

MLServerUrl defaults to http://127.0.0.1:8888; MLPredictPath to /predict_ensemble; MLTrainPath to /online_update. The currently supplied backend returns NO_LEGACY_MODEL_RUNTIME for legacy prediction, so customers must not assume the older EnableOnlineTraining, MLTrainPositiveOnly, EnableMLReverse, OnlineTrainingMode, or MLUseGPU properties provide an active production model path.

Signal Encyclopedia

Three evidence streams: Depth updates show displayed bid/ask liquidity; Last trades show executed transactions; price bars contextualize movement. Depth decreases alone do not establish cancellations, and a named liquidity signal does not identify a particular participant.

Complete signal encyclopedia

Signal lifecycle

detected event → indicator series/confirmation snapshot → strategy eligibility and risk/ML/Flow gates → submitted order → fill/result. Only the final two are orders. The strategy reads BookMap series including Absorption, Exhaustion, Iceberg, Whale, Liquidity Wall, Spoof, and Flash-related values; detector mechanics are summarized from an additional source audit; this customer guide does not disclose proprietary formulas.

Seven BM Liquidity Signals

Open all seven signals in the Interactive BM Visual Lab →

Visual signal laboratory

Each animation below represents a different market-data sequence. The motion is tied to the meaning of the signal: absorption shows execution against a holding queue; exhaustion shows participation fading; iceberg shows repeated refills; Whale shows a clustered tape burst; Wall shows persistent depth; Spoof shows display → pull → reaction; Flash Magnet shows rapid depth growth followed by price attraction.

These are educational diagrams built to explain the logic to customers. They are not live market recordings, profitability examples, or a disclosure of proprietary detector formulas.

BM SIGNAL 01 / 07

Absorption

Heavy execution reaches a price level, but resting liquidity repeatedly holds or reloads and price fails to travel proportionally.

Step 1Aggressive orders hit

Step 2Queue absorbs / reloads

Step 3Price displacement stays limited

Step 4Freshness & distance decide entry

How to read this signal

Core ideaExecuted volume is large compared with price movement.

What confirms itDisplayed queue persistence, refreshes and minimum executed volume.

What can invalidate itStale evidence, too much distance, or missing required queue behavior.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Use BM Absorption	On	Master switch for the BM absorption detector.	Off removes this signal from BM entry eligibility.
Minimum Displayed Queue	50	Minimum visible resting liquidity considered meaningful at the level.	Higher values demand a larger displayed queue; lower values make the detector more sensitive.
Flip Side	Off	Controls whether the interpreted trade direction is inverted.	Enable only when you intentionally want the opposite directional mapping.
Near-Edge Fraction	0.35	Defines how close activity must be to the relevant edge in the legacy path.	Smaller/larger values tighten or widen the accepted edge zone.
Reaction Ticks	1	Minimum price response used by the legacy reaction check; 0 disables that check.	Higher values require a larger reaction before qualification.
Link / Window Sec	5	Time window used to connect queue and execution evidence.	Shorter windows demand tighter timing; longer windows tolerate slower sequences.
Minimum Hits	1	Minimum number of qualifying interaction events.	Higher values require repeated evidence before the signal can qualify.
Minimum Executed Volume	200	Minimum traded volume required around the level.	Higher values filter out lighter interactions.
Queue Hold %	50	How much of the displayed queue must remain/hold during the event.	Higher values demand stronger persistence of displayed liquidity.
Minimum Refresh Count	2	Minimum replenishment/refresh observations.	Higher values demand more evidence that liquidity is refilling.
Reload Tolerance (contracts)	20	Tolerance used when comparing queue reloads.	Larger tolerance accepts more variation between refreshes.
Signal Hold Sec	5	How long a qualified signal remains available.	Longer hold keeps the signal eligible for more time; shorter hold requires faster entry.
Require Fresh At Entry	On	Requires the signal to still be fresh when the order is considered.	Turning it off allows older qualified evidence to remain usable.
Entry Max Distance (ticks)	6	Maximum distance allowed between current price and the detected absorption level.	Smaller values require entry closer to the detected level.
True Entry Logs	On	Records qualified/submitted absorption events for review.	Does not strengthen the signal; it only adds audit/analysis records.
Recent Diagnostic Buffer	On	Keeps recent absorption diagnostics available for export.	Useful for research and support; does not alter the entry logic.
Diagnostic Export Window	3	Controls the recent diagnostic window used when exporting.	A larger value includes a broader recent diagnostic slice.

BM SIGNAL 02 / 07

Exhaustion

The move begins with meaningful activity, then the available liquidity/activity thins and follow-through fades.

Step 1Build a recent baseline

Step 2Depth/activity depletes

Step 3Thin state stays stable

Step 4Reaction/freshness gates entry

How to read this signal

Core ideaParticipation weakens after an active move.

What confirms itDepletion versus baseline plus thin-state persistence.

What can invalidate itInsufficient depletion, stale evidence, or price too far from the event.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Use BM Exhaustion	On	Master switch for exhaustion detection.	Off prevents exhaustion from creating a BM candidate.
Threshold	120	Primary size/activity threshold used by the exhaustion path.	Higher values demand stronger initial activity before depletion matters.
Minimum	50	Lower bound for the thin/depleted state.	Lower values require a more extreme reduction; higher values accept less thinning.
Baseline Lookback Sec	10	Time used to establish normal recent liquidity/activity.	Longer lookback smooths the baseline; shorter lookback reacts faster.
Minimum Depletion %	35	Minimum percentage reduction versus the baseline.	Higher percentages demand more obvious exhaustion.
Minimum Thin / Stable Sec	1	How long the thin state should remain stable.	Higher values reduce brief one-tick depletion events.
Reaction Ticks	1	Optional price reaction requirement; 0 disables it.	Higher values require more visible reaction.
Signal Hold Sec	2	Lifetime of the qualified exhaustion signal.	Short hold makes the entry more timing-sensitive.
Use Adaptive Thin Cap	Off	Allows the thin threshold to adapt to recent conditions.	On can make the threshold respond to changing depth/activity.
Require Fresh At Entry	On	Requires current exhaustion evidence at entry time.	Off can allow older evidence.
Entry Max Distance (ticks)	3	Maximum distance from the exhaustion level.	Smaller values force tighter proximity.
True Entry Logs	On	Stores qualified exhaustion entry records.	Logging only; no direct signal-strength effect.
Recent Diagnostic Buffer	On	Stores recent exhaustion diagnostics for review/export.	Research/support feature, not an entry filter.
Diagnostic Export Window	3	Amount of recent diagnostic context exported.	Higher values preserve more recent context.

BM SIGNAL 03 / 07

Iceberg

Repeated executions occur near the same price while displayed liquidity replenishes, creating more cumulative execution than one visible queue would suggest.

Step 1Trade hits the level

Step 2Displayed size reloads

Step 3Reload cycle repeats

Step 4Refresh/volume rules qualify

How to read this signal

Core ideaRepeated replenishment-like behavior at one level.

What confirms itPrint count, cumulative volume, reload count and price tolerance.

What can invalidate itLarge trade gaps, stale level data, insufficient refreshes or distance.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Use BM Iceberg	On	Master switch for iceberg-style replenishment detection.	Off disables iceberg as a BM entry source.
Minimum Trade Prints	80	Minimum number of qualifying prints/interactions.	Higher values require more repeated trade evidence.
Minimum Executed Volume	350	Minimum cumulative executed volume near the level.	Higher values demand more actual traded volume.
Price Tolerance (ticks)	1	Allowed price variation while linking executions to one iceberg event.	Higher tolerance groups activity across a wider price band.
Min Reload Excess (contracts)	30	Minimum excess replenishment beyond expected displayed liquidity.	Higher values demand stronger refill evidence.
Flip Side	On	Inverts the default directional interpretation.	Use according to the desired response mapping for this detector.
Max Trade Gap Sec	2	Maximum gap allowed between linked executions.	Smaller values require a tighter sequence of prints.
Min Stable Sec	3	Minimum stability time for the detected level.	Higher values reject short-lived levels.
Signal Hold Sec	1	How long the iceberg signal remains eligible.	Short values demand immediate reaction/entry.
Min Refresh Count	5	Minimum number of observed reloads.	Higher values demand more clear replenishment cycles.
Reloads To Bypass Stable Sec	5	Enough reloads can satisfy the event even when the full stability time is not reached.	Higher values make that bypass harder to achieve.
Min Executed % Of Max Display	150	Executed volume required relative to the largest displayed size.	Higher percentages demand more execution than the visible peak size.
Displayed Size Hold Slack %	80	Tolerance for how much displayed size can vary while still treated as the same level.	Higher slack tolerates more queue-size fluctuation.
Disappear Grace Sec	2	Grace period for a briefly missing level.	Longer grace allows short disappear/reappear sequences to remain linked.
Max Level Update Age Sec	1	Maximum acceptable age of level data.	Lower values require fresher depth updates.
Require Level At Entry	On	Requires the replenishing level to still exist when entry is considered.	Off allows entry after the level is no longer displayed.
One Entry Per Iceberg Event	On	Prevents repeated entries from the same detected event.	Off can permit multiple entries if other guards allow them.
Entry Max Distance (ticks)	2	Maximum distance from the iceberg level.	Smaller value requires tighter location.
Show Live Line	On	Displays the active iceberg level on the chart.	Visual only.
True Entry Logs	On	Records qualified iceberg entries.	Logging only.

BM SIGNAL 04 / 07

Whale

A cluster of unusually large prints forms inside a short time and price band, indicating a concentrated burst of tape activity.

Step 1Collect prints

Step 2Aggregate inside burst window

Step 3Compare size / optional DOM evidence

Step 4Debounce & proximity gate entry

How to read this signal

Core ideaLarge activity is concentrated in time and price.

What confirms itAggregate size, burst window, price tolerance and optional DOM fallback.

What can invalidate itStrong opposing bar, debounce, or excessive entry distance.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Use BM Whale	On	Master switch for large-print / burst detection.	Off disables Whale candidates.
Threshold	300	Primary aggregate size threshold shown in the panel.	Higher values require larger bursts.
Use Adaptive Threshold	Off	Lets the size threshold adjust to recent activity.	On can scale sensitivity with changing volume conditions.
Burst Window (ms)	300	Time window used to aggregate prints into one burst.	Shorter values require tighter clustering.
Burst Price Tolerance (ticks)	2	Maximum price spread allowed inside the burst.	Higher values group prints across a wider price area.
Entry Proximity (ticks)	5	Maximum distance from the burst level for entry.	Smaller values require tighter proximity.
Signal Hold Sec	6	How long the Whale event remains eligible.	Longer values give more time to act on the event.
Reject Strong Opposing Bar	On	Blocks a Whale candidate when a strong bar is moving against the signal.	Off ignores this bar-direction safety check.
Opposing Body Min (ticks)	2	Minimum opposing candle body considered strong enough for rejection.	Higher values require a stronger opposing candle before blocking.
Min Seconds Between Trades	3	Debounce between Whale-triggered trade opportunities.	Higher values reduce repeated Whale entries.
Skip Debounce	Off	Allows the detector to bypass normal debounce when enabled.	On increases re-trigger responsiveness.
Flip Side	Off	Inverts the interpreted direction of the Whale event.	Use only when intentionally reversing the default mapping.
Show Live Whale Line	On	Draws the active Whale reference level.	Visual only.
Recent Diagnostic Buffer	On	Keeps recent Whale diagnostic context.	Research/support only.
Diagnostic Export Window	3	Controls how much recent diagnostic context is exported.	Higher values include a wider recent window.
True Entry Logs	On	Stores qualified Whale entry events.	Logging only.

BM SIGNAL 05 / 07

Liquidity Wall

A large resting depth level stands out versus nearby depth, remains stable long enough and stays close enough to current price to matter.

Step 1Detect unusually large depth

Step 2Track stability & drift

Step 3Price approaches within proximity

Step 4Fresh wall can become BM candidate

How to read this signal

Core ideaPersistent depth is materially larger than its surroundings.

What confirms itThreshold, relative-to-average depth, stability and freshness.

What can invalidate itWall disappears, drifts too far, goes stale or price moves away.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Wall Engine Mode	Legacy	Selects the wall detection engine/mode exposed by the panel.	Changing mode changes which wall workflow is used; use only supported modes in your build.
Use BM Liquidity Wall	On	Master switch for Liquidity Wall detection.	Off disables Wall candidates.
Threshold	120	Minimum displayed depth required for a wall.	Higher values require a larger resting level.
Proximity (ticks)	3	Maximum distance from current price where the wall is relevant.	Smaller values focus on walls closer to price.
Stable Sec Req	3	Minimum time the wall should remain stable.	Higher values reject short-lived large orders.
Max Drift Ticks	1	Maximum price movement of the tracked wall while still considered the same event.	Higher values tolerate more movement.
Disappear Grace (sec)	1	Grace period if the wall briefly vanishes.	Longer grace tolerates temporary disappearance.
Signal Hold Sec	2	How long a qualified wall remains eligible.	Longer hold gives more time for entry after qualification.
Min Relative To Avg Depth	1.5	Wall size required relative to normal surrounding depth.	Higher values demand a more exceptional wall.
Depth Stale Sec	1	Maximum age of depth information accepted.	Lower values require fresher order-book data.
Require Fresh At Entry	On	Requires the wall evidence to still be current at entry.	Off can allow an older qualified wall.
Direction Mode	NORMAL	Controls directional interpretation of the wall.	Alternative modes can reverse or alter direction mapping if available.
True Entry Logs	On	Records qualified Wall entries.	Logging only.
Recent Diagnostic Buffer	On	Keeps recent Wall diagnostics.	Research/support only.
Diagnostic Export Window	3	Controls the recent diagnostic window exported.	Larger values preserve more context.

BM SIGNAL 06 / 07

Spoofing Reversal

A large displayed order is tracked, persists, then a significant portion is pulled before much of it executes; a fast price reaction can qualify the reversal heuristic.

Step 1Large order appears

Step 2Order remains stable

Step 3Liquidity is pulled

Step 4Reaction occurs inside window

How to read this signal

Core ideaDisplay → persistence → withdrawal → reaction.

What confirms itMinimum pull %, low executed share and timed price reaction.

What can invalidate itToo much execution, insufficient pull, stale event or no reaction.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Use BM Spoofing Reversal	On	Master switch for the spoof-reversal heuristic.	Off disables Spoof candidates.
Threshold	80	Minimum displayed size used to begin tracking a potential spoof event.	Higher values focus on larger displayed liquidity.
Proximity (ticks)	6	Maximum distance from price where the displayed order matters.	Smaller values restrict tracking to levels closer to price.
Stable Sec Req	2	Minimum time the large displayed order should remain before a pull can qualify.	Higher values require more persistence before disappearance.
Max Drift Ticks	2	Maximum movement allowed while tracking the same displayed order.	Higher values tolerate more price-level drift.
Disappear Grace (sec)	1	Time allowed for the tracked order to disappear and still belong to the same event.	Longer values tolerate slower pull sequences.
Min Pull %	60	Minimum percentage of displayed liquidity that must be removed.	Higher values require a more substantial withdrawal.
Reaction Ticks	1	Minimum price reaction after the pull.	Higher values demand stronger follow-through.
Reaction Sec	1	Time window in which the reaction should occur.	Smaller values require a faster response.
Max Executed %	50	Maximum share allowed to execute before disappearance; helps separate pulling from genuine filling.	Lower values require that less of the order trade before it disappears.
Signal Hold Ms	1000	How long the spoof event stays eligible.	Longer values keep it available for more time.
Require Fresh At Entry	On	Requires the event to still be fresh at entry time.	Off allows older events.
Entry Max Distance (ticks)	3	Maximum price distance from the event level.	Smaller values require closer entries.
True Entry Logs	On	Stores qualified spoof-reversal entries.	Logging only.
Recent Diagnostic Buffer	On	Keeps recent spoof diagnostics.	Research/support only.
Diagnostic Export Window	3	Controls the recent diagnostic context exported.	Higher values include more recent context.

BM SIGNAL 07 / 07

Flash Magnet

Displayed depth expands sharply near price, persists long enough and is followed by a timely attraction/reaction of price toward that level.

Step 1Depth size jumps

Step 2Event passes distance & persistence

Step 3Price moves toward the level

Step 4Freshness/direction rules decide eligibility

How to read this signal

Core ideaFast depth growth becomes an attention/attraction level.

What confirms itSize increase, relative depth, persistence and attraction window.

What can invalidate itToo far/too close, insufficient size growth, weak attraction or stale event.

Parameters in the Xtrend panel

Parameter	Example shown	What it means	What changing it does
Use BM Flash Magnet	On	Master switch for Flash Magnet detection.	Off disables Flash Magnet candidates.
Min Ticks From Price	1	Nearest allowed distance between the flash level and current price.	Larger values ignore flashes that appear too close.
Max Ticks From Price	8	Farthest allowed distance for the flash level.	Smaller values focus only on nearby flashes.
Min Size	100	Minimum displayed size required for the event.	Higher values demand a larger depth event.
Min Size Increase	5	Minimum rapid increase in displayed size.	Higher values require a sharper jump.
Relative To Avg Depth	1	Required size relative to recent average depth.	Higher values require the flash to stand out more from normal depth.
Maximum Attraction Confirmation	3000	Maximum confirmation window shown by the panel for price-attraction/reaction behavior.	Smaller values require a faster confirmation sequence.
Min Persistence Ms	50	Minimum time the new depth must remain present.	Higher values reject ultra-brief flashes.
Minimum Attraction Ticks	2	Minimum price movement toward the flash level used as attraction evidence.	Higher values require a larger approach.
Require Candle Direction	Off	Requires candle direction to agree with the configured Flash logic.	On adds directional candle confirmation.
Signal Hold Ms	3000	How long a qualified Flash event remains available.	Longer values give more time after detection.
Require Fresh At Entry	On	Requires fresh Flash evidence when entry is considered.	Off allows an older event.
Entry Max Distance (ticks)	8	Maximum distance from the flash level at entry.	Smaller values require price to remain closer to the event.
Debug	Off	Enables additional diagnostic detail.	Use for troubleshooting, not normal customer operation.
Recent Diagnostic Buffer	On	Keeps recent Flash diagnostics.	Research/support only.
Diagnostic Export Window	3	Controls the recent diagnostic window exported.	Higher values include more context.
True Entry Logs	On	Records qualified Flash entries.	Logging only.
Reverse Flash Magnet	On	Reverses the default directional interpretation when enabled.	Use only when the intended strategy configuration calls for reversed Flash direction.

Shared BM controls that affect the seven signals

These settings are not one detector by themselves. They change how the seven signals are ranked, routed or adapted after a detector qualifies.

BM signal coordination

• Use BookMap Signals — master switch for BM signal participation.
• Q History Len / BM Hist Len — history windows used by BM evaluation and stability logic.
• Stable Evaluations Required — number of consistent evaluations before accepting an updated BM state.
• Min Seconds Between BM Signal — global spacing between accepted BM events.
• Show Accepted BM Markers — displays accepted BM markers on the chart.

Signal priority

• Priority Absorption
• Priority Exhaustion
• Priority Iceberg
• Priority Whale
• Priority Liquidity Wall
• Priority Spoof

Priorities resolve competing BM candidates. They do not make a weak detector stronger; they decide which qualified event wins when several are available.

BM order routing

• Order Mode — chooses the BM order style.
• Breakout Offset (ticks) — offsets breakout-style placement.
• Limit Offset (ticks) — adjusts limit placement relative to the reference level.
• Cancel if Runs Away (ticks) — cancels a working entry when price moves too far away.
• Abs Near-Edge Fraction — absorption-specific near-edge placement control in the related order path.
• Per-signal ATM templates — lets Absorption, Exhaustion, Iceberg, Whale, Wall, Spoof and Flash use their own ATM template when enabled.

BM Auto Adjust

• Enable BM Auto Adjust — turns adaptive BM tuning on/off.
• Profile — selects the adjustment profile such as Balanced.
• Lookback Samples / Minimum Samples — controls the evidence window and minimum sample count.
• Update Every (sec) — adjustment frequency.
• Adjustment Strength % / Smoothing % / Maximum Change % — controls how strongly and how quickly parameters can move.
• Freeze On Active BM Signal and Freeze With Order / Position — prevent parameter movement during sensitive live states.
• Show Diagnostics — exposes adjustment diagnostics for review.

L1 Fast Execution

• Execution Engine and Limit Placement — select the fast-entry path and passive/marketable placement style.
• Breakout Offset and Maximum Spread — control acceptable placement/spread conditions.
• Maximum L1 Age (ms) — rejects stale top-of-book data.
• Entry TTL (ms) — maximum lifetime of a working fast entry.
• Cancel Run-Away (ticks) — abandons a working entry if price escapes.
• Require BM Reference — requires a valid BM reference level for that path.

Diagnostics and exports

• True-entry logs and recent diagnostic buffers are for analysis/support.
• They do not increase signal strength and should not be described as trading filters.
• Customer documentation should show the feature name, not a developer PC path. Installation/export folders are documented separately.

Trading Modes

Trading modes

EntryCombineMode (; active logic ) controls core-versus-BookMap eligibility.

Risk & Orders

Risk and order management

The actual order owner is NinjaTrader strategy code. Before enabling, verify quantity, account, session and protection settings in the installed runtime. A rejected candidate is not necessarily a risk failure: it may have failed signal freshness, data, mode, ML, L2, position/order, or routing guards.

Verified execution facts: PlaceEntryUnifiedGated owns final submission; Flow AI runs before a submitted entry; terminal results write ledger records after submission/fill lifecycle; legacy versus L1Fast BookMap execution is selectable. L1Fast plans from fresh best bid/ask; Passive uses bid for buys/ask for shorts, while Marketable uses ask for buys/bid for shorts while retaining a limit cap ().

The accessible audit does not establish active implementation of break-even, trailing stop, max trades/day, prop-firm drawdown, partial-fill recovery, connection-loss recovery, or exact currency/tick semantics. Treat all as runtime verification required, not product claims.

Chart Controls

Chart and Control Center controls

The separate desktop Control Center is source-verified as a local client: it starts/queries the local API, displays health/status, and cannot command NinjaTrader. Panel configuration/performance data are local runtime files. Closing its panel requests shutdown only of the backend it owns.

Safety rule for any runtime-tested CXL/FLAT control: use simulation first, identify exact account/instrument scope, record whether confirmation appears, and verify action through NinjaTrader order/position state—not a button color alone.

XtrendBookMap

The supplied source-audit review includes XtrendBookMap and describes its market-depth and Last-trade detector event paths. Each BM signal applies its own conditions for size, proximity, executed prints, refreshes, timing, or price reaction. Indicators must be installed with compatible dependencies and a feed capable of supplying required market-depth data. Exact screenshot labels and active runtime values still need confirmation in NinjaTrader.

What is verified: the strategy reads its signal series and snapshots for Absorption, Exhaustion, Iceberg, Whale, Liquidity Wall, Spoof, and Flash-related context; depth availability is material. Missing dependency source is an installation/release blocker. Obtain the matching indicator .cs source/export, then re-run the property inventory before publishing this chapter.

XtrendFootprint

The subsequent indicator-source audit included XtrendFootprint and verified that the strategy uses Footprint-derived evidence in selected confirmation paths. This does not establish that every optional Footprint confirmation is enabled in a customer template, nor does it verify the installed chart display.

Verified strategy integration: optional BM Wall, Spoof, and Absorption confirmation can require Footprint readiness and evaluate source-defined attack/rejection or momentum conditions. When Block If Data Missing is true, missing required footprint history blocks that enabled confirmation pathway. .

XtrendVWAP

The subsequent indicator-source audit included XtrendVwap; nevertheless, the only setting directly supported by the existing configuration catalog here is EnableVWAPContext=true: off records VWAP context as unavailable/null and source says trading behavior is unchanged (). Do not infer the exact session reset, plot layout, bands or trade-routing impact from a screenshot; validate the installed indicator settings and strategy integration before making a trading claim.

Machine Learning

Machine learning and Flow AI

Two paths exist. Legacy ML properties point to /predict_ensemble, but the supplied V10 backend reports NO_LEGACY_MODEL_RUNTIME; do not configure it as a functioning production confirmation model. Flow AI is the current documented integration: NinjaTrader posts immutable candidate snapshots to /predict_flow; inference requires a validated artifact; prediction itself does not read or train on ledger files.

In GATE, invalid/no model responses follow AI If Unavailable: ALLOW preserves the entry, BLOCK rejects it. SHADOW and ADVISORY do not block through FlowAiEntryAllowed. Feedback happens asynchronously after a terminal result, only when learning is on and update mode is not Off. Ledger records must be under %LOCALAPPDATA%\\XtrendAlgoV10\\ledger for the desktop learner to accept them.

L2 Micro Mode: Off disables; Advisory calculates without blocking; ML Feature records evidence without blocking; ConfirmEntries requires fresh evidence that meets probability/evidence thresholds. Context is explicitly telemetry/research-only in its description; do not market it as an active entry confirmer without a separate runtime proof.

Practical Workflows

Educational examples

These are workflow examples, not recommendations or profitability claims.

1. Simulation core-only: Select CoreOnly, leave optional gates off, verify a detected core event versus submitted order in NinjaTrader logs.
2. BM-only research: Ensure depth/BookMap dependency is installed, use BMOnly, enable one signal family, and review diagnostics without assuming chart events trade.
3. Core + BM confirmation: Use CoreAndBM; begin with default freshness behavior. Expect fewer eligible candidates because both sides must qualify.
4. L2 confirmation experiment: Set L2 Micro Mode to ConfirmEntries; 5 depth levels, 1000 ms freshness, 0.60 threshold and 0.25 evidence are code defaults. Compare blocks in simulation.
5. Flow AI confirmation: Start licensed local desktop service, confirm VALIDATED_MODEL, enable AI Confirmation and GATE, and decide deliberately whether unavailable should ALLOW or BLOCK. Test both outcomes in simulation.
6. Manual monitoring: Keep automated strategy disabled; use indicator visual events strictly as research and practice interpreting stale/missing data.

Troubleshooting

Troubleshooting

Customer FAQ

How does the Interactive Visual Lab relate to the real strategy?

It is an educational visualization of the documented signal concepts using synthetic events. It is not a live NinjaTrader data stream, a strategy tester, a reconstruction of source calculations, or a profitability demonstration.

Does a liquidity event guarantee an order or a fill?

No. Detector acceptance, strategy entry eligibility, order submission and actual fill are separate stages with additional gates and exchange/broker outcomes.

Does a Spoofing or Iceberg label prove market manipulation or hidden orders?

No. These are names of heuristic patterns inferred from displayed depth and executed trades; market data alone cannot prove intent or identity.

Should I copy the defaults printed in this guide?

No. Confirm the effective values in the installed chart and strategy template, especially for parameters synchronized by the strategy.

Customer FAQ

Does a chart signal mean an order was placed? No. Detection, eligibility, submission, and fill are separate stages.

Does the desktop app trade for NinjaTrader? No verified desktop-to-NinjaTrader command path exists.

Can I use Flow AI without a model? The app starts, but Gate behavior follows AI If Unavailable; a validated model is required for a valid Flow prediction.

Why are BookMap features unavailable? They require the matching custom indicator and suitable market-data/depth feed.

Does Context change trades? The exposed description says it captures telemetry and does not change entry/routing/risk/BM/L2/ML decisions.

Can I rely on the old ML endpoint? No; supplied backend reports no legacy model runtime.

What is the safest first test? A simulation account with one feature family, logging, and a clear separation between visual events and orders.