Skip to content

P-01 / LQC

LeoLogic Quantitative Core

A remote operator console for Interactive Brokers, built as a private Discord bot — market data, signals, and backtests all run from a chat command, not a web dashboard. Live order execution is gated off behind measurable validation criteria. Intentionally paused since May 2026 while execution priority sits with Half-Life and LeoLogic OS; reactivation requires a runtime evidence refresh before any further build work.

Status
Parked — idle since 2026-05
Domain
Markets / quant
Stack
Python / Discord Bot / IBKR API / ib_insync
[P-01]LQC
PRIVATE CORE

Technical record

ARCHITECTURE ONLY

LQC is operated entirely through a private Discord bot — the interaction model is deliberately conversational: an operator command in a chat channel is the interface, not a web UI. The bot connects to Interactive Brokers' paper gateway via ib_insync, runs a technical-indicator signal engine, and drives a backtesting framework with parameter sweeps and trade-level diagnostics — all reachable from chat. The order path is implemented and exercised against the paper gateway, but live execution is held behind an explicit flag — ENABLE_ORDER_EXECUTION stays false until the strategy set clears full-universe backtesting, risk-module stress testing, and a 90-day profitable paper record. Treating the safety interlock as a first-class, documented decision matters more here than shipping the feature early. Command surface and strategy logic are closed; the architecture below reflects the real component design.

TECH STACK

Pythondiscord.pyib_insyncpandasSQLiteDocker

SYSTEM SPECS

INTERFACEPrivate Discord bot
BROKERInteractive Brokers — paper gateway
EXECUTIONPaper only — live gated
SAFETY FLAGENABLE_ORDER_EXECUTION=false
UNLOCK BARSharpe > 1.5 · 90d paper
NEXT REVIEW2026-Q4

SYSTEM ARCHITECTURE

LQC — REMOTE OPERATOR STACK
01
DISCORD OPERATOR CONSOLE— Chat-driven command surface — the entire remote-operate interface
02
IBKR CONNECTION LAYER— ib_insync paper-gateway session — quotes, bars, account state
03
SAFETY INTERLOCK— Input validation + persistent kill switch, gates the engine before any order path
04
SIGNAL ENGINE— Technical-indicator strategy logic, iterated across versions
05
BACKTEST FRAMEWORK— Historical replay, parameter sweeps, trade-level diagnostics
06
JOURNAL LEDGER— Local SQLite trade and account log
07
ORDER GATE— ENABLE_ORDER_EXECUTION flag — live path implemented but held closed
LIVE MODULE — OPERATOR ACCESS
QUANT RESEARCH ·DISCORD BOT ·REMOTE OPS ·IBKR API ·BACKTESTING ·SIGNAL PROCESSING ·SAFETY ENGINEERING