ERTS.DOCS
Product
Real-Time Futures • Operator Guide

ERTS Documentation

This documentation explains how ERTS behaves without code snippets: what each layer does, how risk models differ, how the HUD actions are intended to be used, and how to validate correctness in simulation before going live.

3‑LAYER RISK HUD CONTROL PERSISTENCE RULE CLARITY

Overview

ERTS is a real-time strategy framework designed around a single principle: risk is not a feature — it is the system. The entry logic can be simple; the outcome depends on whether risk is enforced consistently, whether protection is placed immediately, and whether the operator can act quickly under stress.

What ERTS is
Trade lifecycle framework
Permission → Entry → Initial Protection → Dynamic Management → Governance.
What ERTS is not
A “magic entry signal”
No system survives without consistent rule enforcement and clear operator behavior.
Read this first: Evaluate ERTS on behavior and correctness before performance. Confirm PnL accuracy, session resets, stop placement, and HUD actions in simulation.

Installation & First Run

Install the strategy as you would any NinjaTrader 8 strategy. On first run: verify the HUD appears, values populate, and the system detects live positions via the account position feed.

  • Confirm the strategy is operating in real-time mode (not analyzer/optimization mode).
  • Confirm the HUD is visible and does not cover the chart area.
  • Confirm account + instrument total PnL display equals realized + unrealized.
  • Confirm the system recognizes an existing open position and can adopt it.
  • Confirm buttons remain persistent after reload (if persistence is enabled).

Recommended Setup

ERTS benefits from stable structure. Many operators pair it with ADTS Renko to reduce noise and keep decisions consistent. Keep your bar preset stable for weeks so you can evaluate behavior over a meaningful sample.

Do not over-tune. Changing parameters daily produces random outcomes and invalidates your review process.
CategoryWhat to doWhy it matters
BarsUse a consistent structural bar type (often ADTS Renko). Keep the preset stable.Prevents structural drift that changes entries/stops week to week.
PnLVerify total PnL is realized + unrealized (account + instrument).Risk gating depends on the correct operational picture.
StopsConfirm initial stop anchors to structure and updates coherently when size changes.Stops must match exposure — especially when scaling.
SessionsConfirm daily reset boundary matches your trading hours.Prevents yesterday’s blocks from leaking into today.

3-Layer Architecture

ERTS enforces risk across three layers because each layer answers a different question:

  • Account: “Should I trade at all right now?”
  • Instrument: “Should I trade this market right now?”
  • Position: “How is this trade protected and managed?”
Design intention
Reduce random outcomes
Rule enforcement replaces willpower, especially after wins/losses.
Operator benefit
Clarity under stress
You can see why trading is allowed/blocked and what protection mode is active.

Account Layer

The account layer is the session governor. When account-level limits are reached, ERTS can block new trades and/or enforce flattening behavior (depending on configuration).

  • Daily max loss: The “global brake” that prevents continuing after a drawdown.
  • Daily target (optional): Stand down after hitting your plan to prevent giving it back.
  • Session reset: Rules reset at the session boundary so the next day starts clean.
A strict account layer is the simplest way to eliminate revenge trading.

Instrument Layer

Instrument controls exist because different markets behave differently. You may be “fine” on the day overall, but one instrument might be in a regime that doesn’t suit your model. ERTS can stop trading that instrument while leaving others tradable.

  • Prevents one market from draining the account’s daily budget.
  • Supports multi-instrument rotation without “bleed.”
  • Improves review quality: you can identify which market is mismatched.

Position Layer

The position layer focuses on protection and coherent trade management. The key idea is that initial protection is immediate, and optional dynamic stop modes can evolve protection systematically.

The most common failure mode is a size change without a protection update. Always verify scaling behavior in simulation.
Initial stop
Structure-anchored
Commonly anchored to a trend line so protection is not arbitrary.
Dynamic stop
Optional & rule-based
Trend/step/level-driven movement—designed to be predictable, not reactive noise.

Risk Model Comparison

Risk models define how daily limits behave psychologically. Choose one model, keep it stable, and evaluate outcomes over weeks.

ModelBest forOptimizesWatch-outs
OriginalStrict operatorsClarity, predictabilityCan feel conservative during recovery days
StepReactive sessionsAdaptive thresholdsNeeds accurate total PnL; avoid over-tuning
Advanced HybridBalanced operatorsHard brakes + limited flexibilityKeep settings stable; don’t tweak daily

Original Model

The Original model is designed for strict rule enforcement and minimal decision overhead. It is often the best default when you want consistent behavior without nuance.

  • Most predictable gating behavior.
  • Easiest to keep stable and review.
  • Strong fit when you want the platform to prevent rule breaks.

Step Model

Step is for sessions that benefit from controlled adaptation. It can adjust thresholds as the day evolves. This model relies heavily on correct total PnL accounting.

If total PnL is wrong, Step will behave wrong. Verify this before using Step.

Advanced Hybrid Model

Advanced Hybrid is designed for operators who want strict brakes but also structured flexibility. It tends to fit multi-instrument workflows and scaling behavior when tuned conservatively.

  • Hard brakes remain non-negotiable.
  • Flexibility is limited and rule-based.
  • Best when you keep changes slow (weekly at most).

HUD Overview

The HUD is the operator control panel. It is intended to be movable (so it doesn’t cover the chart), and persistent (so your workflow doesn’t reset after reload).

  • Visibility: show status at a glance (trend context, blocks, protection mode).
  • Speed: fast actions for scaling or emergency exits.
  • Safety: actions should not create leftover/accidental orders.

Buttons & Actions

Buttons exist for operator intent. The most common use is 1-lot scaling or rapid flattening. Actions should remain dependable even when other “trade restrictions” would normally block a new entry.

Buy Mkt / Sell Mkt
1‑lot adjustment
Intended for adding or reducing exposure quickly with minimal friction.
Close instrument
Fast flatten
Intended for emergency exits or risk enforcement actions.
Always test HUD actions in simulation. Verify they do not violate your intended stop behavior and do not generate unintended follow-on orders.

PnL Display

Operational gating depends on correct PnL. ERTS is designed to show total PnL (realized + unrealized) at the account and instrument level.

  • Account total PnL: global decision context.
  • Instrument total PnL: market-by-market gating.
  • Position context: protects open risk in real time.

Session Boundaries

Daily limits and targets must reset at the correct session boundary. If the reset boundary is wrong, you may see “blocked” states carry into a new day.

If you trade outside regular hours, verify your session template and reset schedule.

Testing Checklist

Before going live, validate correctness and safety:

  • Correct total PnL (realized + unrealized) at account and instrument level.
  • Initial stop placement aligns with intended structure.
  • Scaling updates protection coherently.
  • HUD actions behave correctly under fast conditions.
  • Session reset occurs at the expected boundary.

Troubleshooting

  • Confirm the strategy is enabled and in real-time mode.
  • Confirm chart panel space is available and not hidden by other chart objects.
  • Reload the chart and verify the HUD position is within view.
  • Verify you are viewing total PnL (realized + unrealized), not one component.
  • Confirm the strategy is reading positions from the account feed.
  • Test with a single instrument to isolate multi-instrument confusion.
  • Check the instrument's session template in NinjaTrader.
  • Confirm your session boundary expectation matches the actual template.
  • Re-test across the boundary and confirm limits reset once.

Disclosures

Futures trading involves substantial risk. This documentation is provided for educational and informational purposes only. ERTS is a tool — it does not guarantee performance or profitability.

Past performance is not indicative of future results. Test in simulation and use risk limits appropriate to your situation.