How the-steelix-flame/chronos works
Chronos simulates an impact-aware market: a user starts a run or submits a strategy, agents and strategies trade against a live matching engine, and market data and outcomes return to the dashboard. The graph reflects README-described integrations where their implementation was not sampled; those subsystem links use only documented paths. The separate Vite frontend is documented as an older, unwired interface.
Main entry points: server.py Engine Transport · bridge.py HTTP / WS Bridge · matching_engine.py Matching Engine · oracle.py Macro Oracle
Components 22
User Interfaces
- Chronos Dashboard
swarm_orchestrator/dashboard/app.js - Legacy Frontend
frontend/src/App.jsx - HTTP / WS Bridge
swarm_orchestrator/bridge.py
Market Runtime
- Matching Engine
swarm_orchestrator/engine/matching_engine.py - Engine Transport
swarm_orchestrator/engine/server.py - Run Persistence
swarm_orchestrator/engine/persistence.py
Trading Participants
- Swarm Orchestrator
swarm_orchestrator/core/loop_manager.py - Engine Client
swarm_orchestrator/core/engine_client.py - Agent Population
swarm_orchestrator/agents - Macro Oracle
swarm_orchestrator/oracle.py
Strategy Execution
- Script API
swarm_orchestrator/analytics/routes_scripts.py - Script Library
swarm_orchestrator/runner/script_store.py - Strategy Sandbox
swarm_orchestrator/runner/sandbox.py - Strategy SDK
swarm_orchestrator/runner/sdk.py - FIX Gateway
swarm_orchestrator/runner/fix_gateway.py
Features And Results
- Feature API
swarm_orchestrator/features/routes_features.py - Market Features
swarm_orchestrator/features - Results API
swarm_orchestrator/analytics/routes_results.py - Results Store
swarm_orchestrator/analytics/results.py
Other components
- User
- SQLite
- Gemini Service
Connections 28
- User → Chronos Dashboard: uses
- User → HTTP / WS Bridge: controls
- Chronos Dashboard → HTTP / WS Bridge: REST / WS
- Legacy Frontend → HTTP / WS Bridge: legacy WS
- HTTP / WS Bridge → Engine Transport: control requests
- Engine Transport → Matching Engine: dispatches
- Matching Engine → Engine Transport: publications
- Engine Transport → HTTP / WS Bridge: market data
- Matching Engine → Run Persistence: writes run data
- Run Persistence → SQLite: stores
- Swarm Orchestrator → Agent Population: drives
- Swarm Orchestrator → Engine Client: uses
- Engine Client → Engine Transport: orders / control
- Engine Transport → Engine Client: market feed / acks
- HTTP / WS Bridge → Macro Oracle: scores news
- Macro Oracle → Gemini Service: requests scoring
- Macro Oracle → Engine Transport: submits orders
- HTTP / WS Bridge → Script API: script endpoints
- Script API → Script Library: reads / writes
- Script API → Strategy Sandbox: launches script
- Strategy Sandbox → Strategy SDK: runs strategy
- Strategy SDK → Engine Transport: submits orders
- FIX Gateway → Engine Transport: FIX orders
- HTTP / WS Bridge → Feature API: feature endpoints
- Feature API → Market Features: invokes features
- Feature API → Engine Transport: starts replay
- HTTP / WS Bridge → Results API: results endpoints
- Results API → Results Store: queries results