Scenario A private WebUI: self-hosted fleet console, live situation, and MM health

[adamant-al]

Context

This is a progress update on Scenario A of the private self-hosted WebUI: one operator console for a fleet of ADAMANT Market-Making Software instances. The product direction is in discussion #49. The matching bot contract is in discussion #48.

Rule for operators: the browser and the WebUI backend never talk to exchanges. Charts, the order book, balances, parameters, and commands all come from each bot’s /api/v1. Exchange API keys stay on the bot.

Scenario B (public subscription WebUI, outbound relay, license token) is not in this drop.

What you can run today

A local WebUI process (Vite UI + Fastify BFF) plus one or more bots with private_webui and a shared HMAC secret. You add each bot by URL. The WebUI stores the fleet registry; the bot does not. Operator accounts, 2FA, and roles live on the WebUI. The bot only verifies a JWT { login, role }.

Sign-in. Operator credentials live on the WebUI (email / ADM / ETH + mandatory 2FA). Each bot only checks the signed JWT — there is no login endpoint on the bot.

Fleet tabs and the market desk

Header tabs are one bot each. Status dots come from JWT GET /api/v1/status (working / degraded / stopped), not from the public liveness probe. Public GET /api/v1/health stays { status, transport } so a reachable bind address does not leak MM quality.

On Market you get candles with bot orders overlaid, a live book with spread, 24h range/volume, pair inventory in coin and USD, and manual limit orders. Clicking the book fills side, price, and amount. Cancel sends { id, market, side } and drops the row when the exchange already treats the order as gone.

Market. Candles, order book, USD inventory, and place-order for PENGUIN/USDT on BiFinance — one tab in a multi-bot fleet.

Parameters and Live situation

Parameters is the full WebUiTradeParams form: master MM switch plus groups that follow bot capabilities (missing trade/mm_*.js stays locked). Liquidity, price watching, ladders, volume trader, analog hints, and the rest edit through PUT /params and live-update over Socket.IO params:updated.

Live situation is a 12-hour strip in this browser: inventory (base + quote USD) and open-order notional by purpose. Bars fill while the bot stays connected here. Yellow hour frames mean that hour was degraded; grey means MM was stopped. The frame hugs the bar, not the full chart height.

On the bot, MM quality is sampled outside trade/mm_*.js. /start (or PUT MM on) stamps equal mm_generalInitTs and mm_generalRestartTs. A process reboot while MM is already on keeps init and bumps restart — so you can tell a clean start from a crash-restart.

Parameters. Master MM switch, 12-hour Live situation (inventory and open orders $), liquidity, price watching, and ladders — groups lock when the module is not in this bot build.

Commands and the audit trail

Commands wraps the same handlers as messenger/CLI: fill, close, make-price, TWAP, transfer, withdraw, queries. Destructive POSTs ask for confirm. The right-hand console is the bot’s markdown feed (balances, cancels, epoch resets).

Events is the WebUI audit log in SQLite: who changed what (admin@… vs bot), parameters vs commands, search/filter/JSON export.

Commands. Fill / close / make-price forms plus the live console — same command set as ADAMANT Messenger and CLI, structured for a desk.

Events. Timestamped parameter toggles and command payloads, attributed to the operator or the bot.

Contract notes (for operators who run both sides)

Piece	Behaviour
GET /health	No JWT. { status, transport } only. Still bound to private_webui_bind_host / allowlist
GET /status	JWT. mmActive, mmState, optional init/restart timestamps, grace, degraded reasons
GET/PUT /params	Full snapshot; PUT applies only dirty slices so unrelated modules are not re-enabled
POST /commands/cancel	Optional side: buy / sell
Roles	read-only JWT cannot write; tokens without role keep legacy full access

Older bots without /status still show up: the WebUI falls back to a fat /health payload.

Tracking

WebUI (public):

• Parent: Adamant-im/adamant-tradebot-webui#1
• First increment (closed): #2
• This increment: #3

Bot API (public):

• #104, #130, this increment #131

Product repos (private / premium reference): adamant-al/adamant-tradebot-webui PR #6, adamant-al/adamant-tradebot-me PR #194. Target branch is dev.

What is not in this drop

• Scenario B: relay, payment session, license scope
• Push of ticker / book / balances over WebSocket (still REST polling ~10s)
• The browser or WebUI talking to an exchange

Feedback belongs here or on the issues above. If you already run Market-Making Software with private_webui, this is the console that sits in front of a fleet.