Weather is its own Quatrix layer, with room for flight, sensors, and maps.
The operational side of Quatrix should feel as polished as the scientific catalog layers. This hub keeps the section usable now, even while several provider integrations remain staged.
Weather + Flight
Forecast, METAR, TAF, and airport-status shell with graceful fallbacks for missing providers.
Weather Network
Ground-station ingestion and telemetry views for user-owned sensor hardware.
Traffic
Starter traffic layer designed to connect field operations back to the science graph.
Sourcing
Materials and supplier workflows that will eventually connect into molecules and materials science.
How this section should behave now
Do not block the UI on missing APIs.
- Forecast, flight, and telemetry cards should always render a coherent dashboard shell.
- When a provider is not configured, the user should see a structured placeholder rather than a broken pane.
- Ground-station workflows should stay tied to Supabase-backed user data and storage patterns.
- Later map overlays, direction finding, and field hardware can slot into the same layout without redesigning the section.
Section role in the larger product
Weather is not a side page; it is part of the reality map.
The weather and telemetry layer connects environmental measurement, field instrumentation, aviation context, and future materials or sensor workflows back into the larger Quatrix graph. This is why the hub sits beside Truth, Space, and Lab instead of hiding in a utility menu.