biniEx Engine Tracker

connecting

Live state of the evaluation plane: which engine each deployment runs on, what the v11 route is returning, and how far the keyword port has got.

Right now

Which engine runs what

Live deployments run v11 or v5, chosen per deployment. Backtests always run v5 — the kernel refuses a backtest by design, so that is a fact rather than a setting.

Backtest engine — v5, always

btstrategywindow p&ltradesdrawdown priced from

Deployments

depstrategyownerenginestate verdictsfallbackerror run

Evaluating processes

podverdictfallbackerror

Kernel coverage

Data feeds

serviceheartbeat ttlstate
feedinstrumentsfresheststalest

Correctness gates