Context
qracer/autonomous.py has an AutonomousMonitor class with trigger logic, but integration into the Server event loop, alert routing, and notification delivery is incomplete. docs/autonomous-mode.md marks this as "구현 예정".
Goal
Wire the autonomous monitor into qracer serve so it actively watches the user's watchlist during trading hours, detects significant moves, and sends alerts.
Scope
- Connect
AutonomousMonitor to the Server tick loop in qracer/server.py
- Implement significance filtering (price move > threshold, volume spike, breaking news) with configurable cooldown
- Route triggered events to notification providers (Telegram poller was recently merged)
- On next
qracer repl startup, include overnight autonomous findings in the session briefing via FactStore
- Add config keys to
config.toml: autonomous.enabled, autonomous.check_interval_seconds, autonomous.significance_threshold
- Integration tests with mocked price feeds
Related
Context
qracer/autonomous.pyhas anAutonomousMonitorclass with trigger logic, but integration into the Server event loop, alert routing, and notification delivery is incomplete.docs/autonomous-mode.mdmarks this as "구현 예정".Goal
Wire the autonomous monitor into
qracer serveso it actively watches the user's watchlist during trading hours, detects significant moves, and sends alerts.Scope
AutonomousMonitorto theServertick loop inqracer/server.pyqracer replstartup, include overnight autonomous findings in the session briefing via FactStoreconfig.toml:autonomous.enabled,autonomous.check_interval_seconds,autonomous.significance_thresholdRelated