Feasibility & Research
This project is built around a simple thesis: if you can log and analyze the airspace using “Software Mode” today, swapping to radio hardware later becomes a data-source change — not a rewrite.
What “High-Fidelity” means here
- High-rate points (10s polling now; faster later with hardware)
- Time-series first (InfluxDB for tracks, speeds, altitudes)
- Registry separation (Supabase for metadata + ghosts list)
- Tripwires (ghost detection + low-altitude geofences)
- Dual-stack narrative (credibility + practical migration)
Roadmap recap
- Foundation: Influx bucket + Supabase schema + Litestar API
- Ingestion: worker polls bounding box, writes points, handles gaps
- Visualization: Next.js + Leaflet tactical map
- Intelligence: ghosts + geofences + alert pipeline
Each phase produces a usable artifact — even before hardware exists.
Ethics & guardrails
Aircraft telemetry is a public broadcast, but “can” doesn’t always mean “should”. Keep logs private by default, avoid doxxing, and treat alerts as cues for analysis — not as proof of wrongdoing.