Repository navigation
Synchronization
Quant App has two distinct synchronization concerns: large market-data copies and small operational/planning state.
flowchart TB
PC[Always-on PC] -->|writes| MySQL[(Canonical market MySQL)]
MySQL -->|checkpointed pull only| Mirror[(Laptop SQLite mirror)]
Laptop[Laptop] -->|reads| Mirror
PC -->|revisioned control/state| Coord[(TLS coordination/operational SQL)]
Laptop -->|revisioned control/state| Coord
Coord --> PC
Coord --> Laptop
PC -. never .-> Upload[Upload laptop mirror rows]
Laptop -. never .-> MySQL
The mirror is strictly PC-to-laptop. Laptop-only data is never uploaded to canonical MySQL. Copy workers use checkpoints/watermarks and tolerate restarts.
Watchlist, Buylist, trade plans, execution queue, device role, operator control, and Live Trading control are revision/fence aware. Writer ownership is explicit; stale devices remain pull-only.
Automatic PC ownership claim is optional and off by default. It requires the expected hostname and a stale/unclaimed fenced claim. After ownership changes, account-wide broker reconciliation and strict persistence/publication must complete before the runtime resumes. Handoff never changes the canonical Live Trading switch.
See Operations and Monitoring before enabling physical sleep/wake automation.
- Home
- Supabase Deployment
- Project Tour
- Quick Start
- System Overview
- Architecture
- Installation and Environment Setup
- Configuration
- User Workflow
- Watchlist and Buy List
- Buy Board and Kanban States
- Scanner and Charts
- Market Data and Database
- Synchronization
- Web/PWA Operator Synchronization
- KIS API Integration
- Current Order Logic
- Order Lifecycle
- Risk and Safety Controls
- Background Jobs and Automation
- Testing
- Operations and Monitoring
- Troubleshooting
- Security
- Glossary