Sentinel Deck v0.2.5 — testers' preview (SUPERSEDED by v0.2.6)

⤴ SUPERSEDED by Sentinel Deck v0.2.6

This release is kept for reference and as a fallback — it is no longer the build to install.

v0.2.6 records what a market fill actually cost you. In this v0.2.5 build, market fills carry no
slip field at all and market order rows log px:0, so entry execution cost is simply absent from
the Ledger. If you are analysing Deck fills from this build, you are measuring exits only — it is not
that entries were free.

The runtime here also ships SentinelCore v1.36.0, nine versions behind. ⚠ Installing this bundle
after a newer one will downgrade Core and break the compile across your whole NinjaTrader tree.
If you keep both, copy the newest bundle's runtime/ last.

---

⚠ This build places real orders, and it is not finished.

It is published for testing, not for trading. Auto-fire has never been validated live — that
is precisely what we are asking you to help us establish. Start on a SIM account.

The Sentinel Deck is a manual discretionary order deck for NinjaTrader 8: its own Buy/Sell surface with
full order types, bracket / breakeven / seven trailing modes, a chart-scoped flatten, an account-tracking
risk card, and a signal reader that can arm you — or fire for you.

It is the first bundle in this repo that can place an order. Everything published before it is read-only.

---

What ships with it — and why

Installing the Deck also installs SentinelCore.Safety.cs, the account-risk layer it gates automation
through: kill switch, governor, drawdown, session rules, sizing. That is deliberate ordering rather than a
bundling accident — safety ships before autopilot. The Deck cannot function without it, and a bundle
missing it would fail to compile the entire bin\Custom tree, not just the Deck.

The safety model — read this before you install

path	behaviour
your click	the kill switch, governor, feed health and news are advisory — displayed, never blocking
auto-fire	fail-closed through the Gate — a hard reason aborts the submit and tells you why

That asymmetry is the design: a human must always be able to act, especially to exit. It also means the
Deck is not a gated tool on the manual path. The band under its header names your account and classifies
it (SIM / REAL orders — prop eval or funded), turning red only when a real account is selected and
auto-fire is armed.

Install

Two ways. Either is fine — pick one, don't do both.

A. Import the NinjaScript archive (one click)

1. Download sentinel-deck-v0.2.5-import.zip below.
2. NinjaTrader → Tools ▸ Import ▸ NinjaScript Add-On… → select the zip.

B. Copy the source (sentinel-deck-preview-v0.2.5.zip, or clone the repo)

1. deck\Indicators\SentinelDeck_v0_2_5.cs → Documents\NinjaTrader 8\bin\Custom\Indicators\
2. all four files in runtime\AddOns\ → bin\Custom\AddOns\
3. NinjaScript Editor → F5.

⚠ sentinel-deck-preview-v0.2.5.zip is source, not an importable archive. Feeding it to
Import gets you "made from an older, incompatible version of NinjaTrader or is not a NinjaScript
archive" — that is NinjaTrader saying it found no Info.xml, not a version problem. Use the
-import.zip, or copy by hand. (Reported by a tester; the import archive was added afterwards.)

Then: open a chart, open Chart Trader (required — the Deck reads the account and instrument from
it), and pick Indicators → Sentinel → Sentinel Deck v0.2.5 (DEV).

Requires NinjaTrader 8. No binaries are shipped — both zips contain source only.

How to report anything

Click Export diagnostics for a bug report in the panel. Explorer opens with the file selected. Attach
it to a Deck preview report.

It captures your build, the account and its classification, every panel setting, the indicators on your
chart, the Deck's log trail and the day's order ledger — so a report needs four lines from you, not twenty.
It is plain text and contains account names and the day's fills; read it before posting.

What we most want to hear about

1. Anything that moved money you did not intend — wrong size, side, or instrument; an exit that did not exit.
2. Auto-fire firing when it shouldn't, not firing when it should, or twice on one bar.
3. A stop that moved the wrong way under any trailing or breakeven mode.
4. FLATTEN THIS CHART touching anything beyond that chart's instrument.
5. The band naming the wrong account, or reading SIM on a real one.

auto-fire BLOCKED: <reason> is the safety system working — please still report it, with the reason, so
we can confirm the block was correct.

Known, no need to report

• Drag-to-attach snap — the grab works; snapping a line to an indicator plot can fail.
• Manual clicks are not gate-blocked — by design (see the safety model above).

Docs

• Tester's guide — every control, what to look for, how to report
• Spec — design, order ownership, telemetry, open questions

MPL-2.0. No warranty — see the disclaimer.
You are responsible for every order placed from your machine.