Field Notes: Deploying the Mariana Array at 6,000 m
Eleven days, fourteen moorings and one pressure hull that did not come back the way it left. The operational record of the deepest Bathys deployment to date.
Bathys turns 4,092 moorings into one operator console: every reading placed on the topology, every anomaly opened with the minutes you have left, every automated action logged for a human to override.
Four things a single instrument cannot do, and what Bathys does instead.
A sensor reports a value.
The array reports where the value is going: gradients are evaluated along the topology, mooring by mooring.
An alarm fires when a threshold is crossed.
An event opens eleven minutes earlier, on the slope of the signal, with the lead time shown next to it.
Automation acts, and you find out later.
Autonomous rules act inside the warning window, log every decision and leave the operator a hold.
The seafloor model is whatever the last survey left.
Every transit is a survey. The bathymetry model is versioned, diffed and never older than the last passage.
Each module answers one operator question. None of them hides a signal to look calm.
Live mooring relationships, cable interdependencies and acoustic relay pathways rendered as a single map. A noisy hop is re-routed before it costs you a reading.
Seismic deviations, cascading current shifts and pressure thresholds surfaced as events, each carrying the minutes you have left to decide.
Ballast release and ascent policies act inside the window. Every action is logged with the rule that fired, and an operator hold always wins.
Bathymetry syncs, model applications and topology changes are versioned. Two states of the array can be compared like two commits.
Battery reserve and hull pressure per mooring, with a flag raised while a vessel is still in range rather than after it has left.
thermocline_alpha, salinity anomaly detection and pressure mapping ship through a secure CLI with a version, a diff, a shadow-sm mode and a one-command rollback.
The engine ingests every mooring, places the reading on the topology, and opens an event on the slope of the signal. Autonomous response runs inside the window it just bought you.
Ingest normalized telemetry from sensor buoys, filter noise, and surface material state changes in real time.
Cross-reference live conditions against historical tide models, current graphs, and defined pressure thresholds.
Execute ballast logic, reroute acoustic relays, and broadcast severity alerts before instability expands.
Eleven days, fourteen moorings and one pressure hull that did not come back the way it left. The operational record of the deepest Bathys deployment to date.
The thermocline_alpha model is now the default thermal stratification model on every Bathys deployment. What changed, what to check, and how to roll back.
Twenty-four sediment turbidity events, all detected before they became visible in the raw trace, all contained by the autonomous ballast policy. What the pattern looks like.
Yes. The own-vessel mode runs the full console offline: topology, events, rules and the system log. Events, logs and model versions synchronize when the vessel is back in range, and the log records the gap.
Existing instruments join the array through a relay buoy that timestamps and normalizes their stream before the first hop. They appear in the topology like native moorings; only the ballast-release policy is limited to Bathys hulls.
Events open on gradients evaluated along the topology, not on single readings, and every event carries its lead time and the moorings that support it. Operators can close an event with a hold, and that hold trains nothing silently — it is logged and reviewed in the shadow-sm deployment report.
You do. A model update arrives through the secure CLI with a version and a diff, runs in shadow-sm mode next to the current one, and is applied when you say so. Rolling back is one command, and the system log keeps both versions comparable.
The programme that collected it. Bathys keeps anonymized array statistics to improve the models unless you opt out, and never publishes a survey contribution without the owner’s consent.
Before a single mooring is wet, we connect the engine to your existing feed and show you every event it would have opened, with the lead time it would have given you.