SeaCommons live drift overview

SeaCommons receives structured distress events from webhooks, Telegram, Twilio WhatsApp or SMS, ingests vessel and shipboard data, and renders a common operational picture locally in the browser. It is built for crews, operators, NGOs, watchdog organisations, security researchers and field teams that need immediate visibility without adding another opaque dependency to the chain.

The platform links observation, decision support and evidence. A single event can trigger drift computation, weather-derived survival context, anomaly escalation, vessel-state overlays and a signed forensic packet that preserves timing, context and computational output. The same substrate can support humanitarian SAR, maritime monitoring and selected defensive or conflict-adjacent tooling.

The Red Sea and Strait of Hormuz — two of the world's most critical energy chokepoints — have seen sustained armed incidents since 2023. The Central Mediterranean remains the world's deadliest migration corridor, with systematic documentation of pushbacks and duty-to-rescue failures. In all three zones, the gap between what happened and what can be proven in a court or tribunal is measured in the quality of technical evidence.

SeaCommons produces reproducible, signed, time-stamped drift reconstructions. This is not an operational command system — it is a decision-support and evidence platform designed for actors who need to work with maritime data without being absorbed into the surveillance architectures they are trying to document. Deployment, permitted uses and governance are detailed in the technical documentation.

SeaCommons is not limited to maritime drift. In the current `seacommons` repository there is an ionospheric anomaly layer that tracks planetary Kp and TEC perturbations, using Madrigal-style vertical TEC baselines to detect anomalous disturbances. When a TEC spike exceeds threshold while geomagnetic conditions remain relatively quiet, the detector can classify the event as `ballistic_candidate` rather than a generic atmospheric anomaly.

That signal is then useful inside correlation, not on its own. The correlation engine upgrades threats to `ballistic_confirmed` when ionospheric evidence aligns with infrasound or seismic channels at sufficient confidence. In parallel, the drift stack also includes a `BallisticTerminal` solver for terminal-phase trajectory estimation, impact point projection and fragment radius output. So the ballistic aspect in SeaCommons is already present as both sensing logic and terminal modelling logic, even if the current page has so far foregrounded the maritime side more heavily.

The current `seacommons` build is not just a drift simulator. It now includes `core/api/routes` for alerts, drift, anomaly, forensic, ingest, integrations, vessels, probability and weather, plus dedicated modules for sensors, chokepoints, ionosphere and shipboard event routing.

The frontend runtime is a React + Vite watch interface with map layers for AIS, weather, drift, forensic output, GNSS and ionosphere, while the backend also exposes ballistic terminal modelling and multi-sensor threat correlation paths for scenarios beyond SAR alone.

The live dashboard runs in your browser as a single-page React application backed by FastAPI. Select a point on the map, choose vessel type and persons on board, and launch a run. The backend returns a projected track plus 6 h, 12 h and 24 h search cones over the base map.

Full documentation covers architecture, API reference, drift methodology, forensic packet schema, simulation scenarios, ethics and governance framework, and geopolitical deployment context. Deployment is Docker Compose, single-server, air-gapped capable.