What it covers
-
01
Live desk
Start and stop sit next to a pair table: book position, broker position and run flags. Published screens keep the rows as placeholders, so symbols and sizes are not shown.
Live desk: start/stop, pair table and session health. Host name, symbols and sizes are hidden. -
02
Daily P&L
A month calendar and a monthly table hold book and broker P&L per session. Published screens keep the chrome and blur the figures.
Daily P&L: calendar and monthly table. Figures are blurred.
The problem
Live pair state, broker-session health, daily P&L and the order journal sat in different terminals and files. Confirming whether the desk was running, and what the book did that day, meant assembling several screens.
How it was built
The console is a FastAPI app with Jinja2 templates and HTMX partials. The live process writes runtime state locally. The same UI talks to a securities broker gateway for session and fills. Replay and research pages stay separate from the live desk.
What changed
Operators start and stop the desk, read pair state and review daily P&L from one console. Published screens hide host names, symbols, quantities and P&L figures.