How himanshumohanty-git24/rakshaquant works
RakshaQuant is a paper-trading research platform for NSE equities: three paired books receive the same signals, while deterministic, typed-model, and LLM advisors may veto entries. The session evaluates signals, applies risk controls, routes orders through a simulated broker, and records outcomes for replay and comparison. Operators use a token-protected web console or terminal dashboard to inspect and control runs. The graph preserves the documented market, risk, AI, experiment, and console capabilities; some links use README documentation because the corresponding implementation was not sampled.
Main entry points: engine.py Decision engine · runner.py Session engine · oms.py Order management · event_store.py SQLite event store
Components 20
Operator consoles
- Web console
frontend/src/app/routes.tsx - Terminal dashboard
src/dashboard/cli.py - Web API
src/web/server.py
Trading session
- Run manager
src/web/run_manager.py - Session engine
src/engine/runner.py
Decision and execution
- Trade strategies
src/strategies/policy.py - Decision engine
src/decision/engine.py - Risk engine
src/risk/engine.py - Order management
src/oms/oms.py - Exit management
src/oms/exit_manager.py - Simulated broker
src/brokers/simulated/broker.py
Data and AI
- Market data
src/marketdata/history.py - Signal features
src/features/technical.py - Entry advisors
src/decision/advisors/llm_veto.py - LLM router
src/llm/router.py - Decision models
src/decision_models/labels.py
Records and research
- SQLite event store
src/store/event_store.py - Experiment evaluation
src/evaluation/experiment.py - Backtesting
src/backtesting/session.py
Other components
- Operator
Connections 22
- Operator → Web console: uses
- Operator → Terminal dashboard: uses
- Web console → Web API: requests data
- Web API → Run manager: routes control
src/web/server.py - Run manager → Session engine: starts run
src/web/run_manager.py - Terminal dashboard → SQLite event store: reads events
src/dashboard/cli.py - Terminal dashboard → Web API: uses queries
src/dashboard/cli.py - Session engine → Decision engine: runs decisions
src/engine/runner.py - Session engine → Market data: uses feed
src/engine/runner.py - Session engine → SQLite event store: records events
src/engine/runner.py - Decision engine → Signal features: computes context
src/decision/engine.py - Decision engine → Trade strategies: requests proposals
src/decision/engine.py - Decision engine → Entry advisors: requests veto
src/decision/engine.py - Entry advisors → LLM router: requests completion
src/decision/advisors/llm_veto.py - Entry advisors → Decision models: uses classifier
- Decision engine → Order management: submits orders
src/decision/engine.py - Decision engine → Exit management: tracks entries
src/decision/engine.py - Order management → Simulated broker: routes orders
src/oms/oms.py - Order management → Risk engine: checks risk
- Exit management → Order management: submits exits
src/oms/exit_manager.py - SQLite event store → Experiment evaluation: supplies records
- SQLite event store → Backtesting: supplies replay
src/backtesting/session.py