LIVE PRODUCT TRACKER

Bot Platform Status Board

One page to track exactly where the bot product is: what is live, what is staged, what is being built now, and what is left before the next sellable release.

LAST UPDATED
17 Mar 2026
Updated after stale-bot auto-rotation, desk-wide supervisor controls, insufficient-funds funding recommendations, and the latest event-driven runtime work were added.
MAIN DASHBOARD
Live
Adaptive Bot Supervisor, stale-bot auto-rotation, and the separate shock path are live on the main bot stack.
BOT-ONLY STANDALONE
v1.3.3
Latest staged bot-only package with current fixes.
PUBLIC OWNER BUILD
v1.3.3
Public install folders now updated to the current release line.
CORE STATUS
Stable
Live bots, stale-bot auto-rotation, supervisor, shock path, funding recommendations, timeline, backtest lab, rebalance, Telegram and asset page are in.
SELLABLE MODELS
4
Bot only, engine only, engine + bots, and hosted/licensed builds published.
ACTIVE BLOCKER
1
Main remaining work is the live-runtime rebuild: stream-driven market data, queue-based execution, and push updates.
NEXT FOCUS
Live Runtime
Replace polling with shared WebSocket feeds, event-driven bots, and real-time dashboard push.
Current Status
USE THIS AS THE DAILY CONTROL VIEW

Main Bot Platform

The live dashboard includes bot trading, history, backtest lab, portfolio desk, Telegram tooling, live asset inventory, manual sell controls, desk-wide stale-bot watch and auto-replace controls, and the adaptive Bot Supervisor with a separate shock path. The next major track is continuing the runtime rebuild from polling-first to fully event-driven.

Standalone Bot Build

The standalone bot-only package is aligned to the current asset-page and runtime safety fixes, but the supervisor/shock-path and the later live-runtime rebuild phases still need to be rolled into the client builds deliberately.

Commercial State

The four sellable product lines are published: bot only, engine only, engine + bots, and hosted/licensed engine + bots. Public release folders are aligned, the licence admin/login path is fixed, and the hosted package has been refreshed to v1.3.5, and the portfolio deploy path now keeps all selected opportunities instead of truncating a 5-stack to 4. Live bot tuning now also enforces fee-aware profit floors, disables trailing-down on fee-sensitive spot grids, and sizes restart sell ladders from bot-owned inventory rather than assuming general exchange balance.

Live Runtime Priority
THIS IS THE MAIN ARCHITECTURE TRACK NOW

Phase 1 — Market Stream

Replace the shared HTTP polling feed with venue WebSocket managers and REST fallback only after stream failure. One shared stream per venue, not one connection per bot.

Phase 2 — Event-Driven Bots

Move live bots onto event dispatch from ticks and fills, with in-memory bot state as the hot path and async write-through to Postgres.

Phase 3 — Queue Execution

Introduce per-bot order queues, dedupe guards, async confirmation, slippage capture, and faster shock-path exits without human gating.

Version Map
KEEP THIS UPDATED WHEN A BUILD CHANGES
MAIN BOT UI / DASHBOARD
1.3.4
Current live dashboard state with adaptive supervisor, recovery seeding, and market-aware ATR/ADX reconfigure logic running on the main bot stack.
BOT-ONLY STAGED BUILD
1.3.4
Latest staged standalone zip including the current bot automation page, desk trust surfaces, capital model fixes, recovery seeding, and ATR/ADX-aware runtime upgrades.
PUBLIC BOT-ONLY BUILD
1.3.4
Public bot-only package is aligned to the current runtime safety work, desk automation surfaces, recovery seeding, and market-aware ATR/ADX logic.
ENGINE / HYBRID / HOSTED
1.3.4 / 1.3.5
Owned engine and owned engine + bots are on v1.3.4; hosted/licensed bots and full-package lines are on v1.3.5, with version-aware upgrade scripts and aligned public archives now bundled.
Build Board
CURRENT / DONE / NEXT

Current

ACTIVE
  • Adaptive Bot Supervisor, stale-bot auto-rotation, and the separate shock path are live, and Phase 1 of the runtime rebuild is now in place with shared Kraken and Coinbase market streams feeding the live cache.
  • Bot runners now wake on per-pair tick subscriptions instead of sleeping between every evaluation pass.
  • Phase 2 is live: newly placed orders enter a fast confirmation lane and queue-backed execution path instead of waiting on the legacy fill sweep alone.
  • Phase 3 backend work is live: stale Coinbase pairs are now detected individually, heartbeats count toward freshness, REST rescue is used when needed, then targeted resubscribe runs before any full reconnect.
  • The main bot pages now use the dashboard socket for live refreshes, the Trading page no longer opens its own browser-side exchange feed, and bot controls use socket acknowledgements when connected.
  • Version tracking now lives alongside the roadmap in /opt/investment_engine/docs/BOT_RUNTIME_VERSION_HISTORY.md and /opt/investment_engine/docs/BOT_RUNTIME_LIVE_REBUILD_PLAN.md.

Done

SHIPPED
  • Bot timeline, signal history, backtest lab, launch summary, portfolio controls, desk-wide stale-bot watch and auto-replace controls, adaptive supervisor and separate shock path added.
  • Standalone bot-only split created separately from the full engine surface.
  • Telegram trade and profit alerts working in standalone.
  • Bot Assets page added so holdings can be reviewed and unmanaged leftovers sold from the panel.
  • Coinbase dependency and standalone asset-route imports fixed.
  • Public product folders published for all four product lines, with engine-family schema fixed for Postgres 15.

To Do

NEXT
  • Move the remaining live dashboard surfaces onto sockets or managed refresh so there are no stale-feeling live panels left.
  • Reduce supervisor DB writes in apply/log flows even further now that the hot-path reads are collapsed.
  • Tighten cancel and reconcile latency across the remaining order-management flows.
  • Remove the last non-essential polling timers from the wider dashboard shell.
  • Package the supervisor/shock-path feature into the standalone/client bot builds after the runtime architecture direction is stable.