← all research

Window since 2026-09-01 (UTC), 1 bot(s).

BotDateLiveSimMatchSlippage (bps)Fees

Summary: no comparable decisions Mismatches: 0

No slippage records in window (all OBSERVE or no fills).

Reading

  • ✗ MISMATCH means live and replayed frozen decide disagree on a completed-bar date -> investigate data feed or warm-up divergence.
  • Large or systematic slippage vs paper assumption suggests sizing or maker logic needs tuning (P1b/P1c).

Flagship (region-A) — live trades vs traded cache

DateSymActionReasonLive pxCache combinedml_activeCache closeVerdict
2026-09-04AVGObuyentry358.25+0.216True357.90OK
2026-09-04DXCMsellsignal_exit87.81-0.220False87.90MISMATCH (exit w/o flip)
2026-09-04MSCIbuyentry573.58+0.225True573.01OK
2026-09-04VRSKbuyentry185.98+0.165False185.79MISMATCH (entry w/o signal)
2026-09-04WBDbuyentry28.28+0.300True28.25OK

Flagship signal mismatches: 2/5.

Accounting (broker truth vs local model)

Last row 2026-09-08: broker equity=$31,665.11 cash=$0.00 peak=$31,665.11

Pre-2026-09-10 equity.csv rows are local-model (BP era, inflated); post-fix rows are broker truth.

Reading

  • MISMATCH (entry w/o signal) means the live trade's cache bar had combined<=0.05 or ml_active=False -> investigate TOP_K gating or stale cache.
  • MISMATCH (exit w/o flip) on signal_exit without combined<-0.25 -> investigate exit wiring.
  • Accounting WARNINGs point at leverage/sync bugs, not alpha.