SeaCommons live drift simulation
Distress ingestion, weather forcing and drift projection combined into a single operational view for maritime awareness, forensic logging and contested-field monitoring.
18 kn
ENE
1.8 m
0.8 kn
What It Does
System OverviewSeaCommons 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.
Core Capabilities
Functional LayersDistress Ingestion
Receives structured signals from webhook partners, Telegram, Twilio WhatsApp and SMS, then normalizes them into a reviewable internal event model.
Drift Projection
Runs trajectory and search-area estimates through the DriftEngine and OpenDrift runtime, with configurable forcing and advisory GeoJSON output.
Anomaly Correlation
Correlates seismic, infrasound, ionospheric, ADS-B, AIS and other signals into escalated threat states rather than isolated alerts.
Ionosphere + Ballistic
Monitors Kp and TEC perturbations through the ionospheric layer, flags `ballistic_candidate` events and contributes to `ballistic_confirmed` classification when correlated with infrasound or seismic evidence.
Vessel Intelligence
Maintains a vessel registry, shipboard event aggregation and chokepoint counts, supporting both open-water awareness and onboard read-only integration.
Threat Monitoring
Provides a base layer for monitoring spoofing, jamming, dark traffic, chokepoint pressure and other signatures relevant to hostile or strategically sensitive environments.
Weather + Probability
Combines Open-Meteo and CMEMS data with survival and interception logic so operators can score urgency and likely rescue windows.
Forensic Logging
Signs and hashes incidents so the operational record remains auditable, exportable and legally legible after the event.
How It Works
Operational FlowA signal enters from operator input, Twilio, Telegram, webhook, AIS, NMEA or background sensor threads.
The backend validates the payload, enriches context and routes it into drift, anomaly, weather, vessel or probability workflows.
The common operational picture updates with vessels, weather grids, drift cones, alerts, logs and scenario replays in a local browser UI.
A signed packet and append-only event record preserve the operational chain beyond the live moment and into later review.
Why It Matters
Deployment LogicMost maritime software assumes stable connectivity, fixed institutional infrastructure and a narrow operating model. SeaCommons is being shaped for the opposite condition: intermittent access, distributed actors, multi-sensor ambiguity, partial shipboard integration and the need to preserve evidence while still acting in real time. That makes it relevant not only to SAR, but also to border violence documentation, strategic maritime observation and defensive monitoring around contested routes or infrastructure.
Ionosphere and Ballistic Layer
High-Altitude Detection LogicSeaCommons is not limited to maritime drift. In the current `drift` 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.
Current Runtime
Repository StateThe current `drift` update 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.
Documentation
Technical ReferenceThis page is the accessible project presentation: what SeaCommons is, why it exists, and how it operates at a high level.
For architecture, BOM, forensic packet schema, simulation scenarios and vessel integration details, use the dedicated technical documentation.