Sentinel Suite · NinjaTrader 8 · living document·Docs home →

Sentinel Documentation

ℹ This is the published subset. The canonical index lists every document in the working tree; rows pointing at documents that are not part of this repository have been filtered out, so every link here resolves. Nothing is hidden by omission that is not simply unpublished.

The one door into the Sentinel Suite's documentation — a bound set of living documents, four chapters by audience, all in one house style. Start with the reading path that fits why you're here.

Start here — pick your path

• Just want the idea? → the Thesis. What Sentinel is and why, in one read: fuse many honest signals into one fitted decision, grade it against reality, feed the grade back.
• Want the whole thing on one page? → the two visual guides: the Architecture Map (every layer and tool, including the 53-file Python Lab, with honest per-tool status) and the Runtime Topology (what actually runs, who owns each artifact, and the boundaries that bite).
• Want to run or extend it? → the Field Manual. The illustrated, end-to-end manual — from "I have no idea what this is" to "I can run it, extend it, and trust it."
• Here to contribute or plan? → the Roadmap (the engineering pipeline) and the Product Ladder (the open-source product/packaging map).
• Writing code for it? → the Design System (palette, components, build), the ML Spec (schema + the offline Lab), the Dataset Dictionary (corpus syntax, nomenclature & how the Lab reads it), and the Boundary Inventory (every file → rung → bundle).

The chapters

The table above is the curated front door — the reading path, not the inventory. Every document in Docs\ is listed in §Complete registry below.

Complete registry — every document in Docs\

This section is the INDEX OF RECORD (2026-08-03). Before it existed, 41 of 72 documents had nothing linking to them, so Lab\docs\audit.py's orphan check was firing on two thirds of the corpus and meant nothing. ⇒ "Orphan" now means "missing from this registry." A doc not listed here is either new and unregistered, or it should be in _archive\.

Rule for adding a doc: a new .md in Docs\ gets a row here in the same commit. One line, honest status. If you cannot state its status in a line, that is a signal about the document, not about the rule.

Data platform & corpus

Replay & the Conductor

Strategy & signal

Bar types

UI, suite & naming

Reference & meta

Archived — Docs\_archive\

Superseded or pre-Sentinel. Kept, not deleted, because several are only legible as the plan that was wrong.

SENTINEL_REPLAY_FARM_SPEC (answered by the Watch) · EYE_ADJUDICATION (the Eye is dead) · AdvancedSuiteDocumentation · QuickReferenceGuide · FuzzyLogicProjectConversation (all pre-Sentinel).

⚠ 25 of the documents in Docs\ have no status line. (Said that way deliberately: this count is over the whole canonical tree, and the published copy of this index lists only a subset — "25 of these" would be false there while looking freshly checked.) That is the next thing worth fixing: a doc that never states whether it is a plan, a spec or a record cannot be audited for staleness, and this whole sweep started because three documents' status lines had been false for weeks.

The system in one line

SENSORS watch (incl. the order-flow FLUX axis) → CORE carries → COUNCIL decides → BRIDGE / DECK act → GATE guards → LEDGER remembers → LENS grades → LAB learns (the built SQLite data platform fits the ConvictionFloor + per-bar-type weights) — and the grade feeds back into the decision.

Every document here is a living document, rendered from Markdown into the shared Field Manual house style. The Markdown source (.md) sits beside each .html, so the words are versioned as plain text and the look is applied by one shared template.