01 / Execution core
Quant Trading Framework
A local quant workbench where execution, risk, reporting, and research stay in one reproducible loop.
Quidem is not a generic PyPI package. It is a personal trading framework that organizes live or paper execution, terminal interaction, Redis status channels, email reports, exchange access, position risk, backtest research, and logs in one repository.
Repository
/home/lry/Projects/PythonRepo/quidem
Technical Stack
02 / Operating surface
A terminal-first interface keeps long-running trading visible without a web backend.
The TUI uses standard output, ANSI control sequences, colorama, and cross-platform keyboard input to show position direction, market state, key indicators, current price, floating PnL, open events, close events, errors, pause, resume, and exit controls.03 / Risk and review
Redis reporting and backtests make trading behavior observable after the session ends.
Closed trades are queued in Redis for scheduled HTML mail reports, CSV attachments, equity curves, and archive files. Backtest modules reuse core strategy, indicator, and risk code, while HMM, clustering, BOCPD, and diagnostic replay scripts support research and post-loss analysis.


What I Built
Binance Futures REST and WebSocket access are isolated behind ccxt and websocket-client adapters.
Paper mode records simulated orders without touching real exchange order endpoints.
Risk management covers order sizing, leverage, taker fee estimation, stop loss, take profit, cooldown, circuit breaking, breakeven protection, and trailing stops.
The report pipeline decouples the trading loop from email delivery through Redis, Resend, schedule, pandas, and matplotlib.
Backtest and diagnostics reuse core modules to avoid a hard split between research logic and live trading logic.