Marlin-XR Seabed Survey AUV
An autonomous underwater vehicle surveying the export-cable corridor of the Dogger Bank offshore wind farm. The bundled demo ledger: forty items seeded across all eleven lifecycle stages, from the mission brief to the deployment procedure.


What this class is held to
The recipe for this system class encodes its standards as tracked obligations, so the design is proven against them rather than tested against them at the end.
- MCA MGN 664
- IMCA S 019
- Marine Licence (MMO)
- UNCLOS Art. 60/80
One dive, a fixed corridor, and no room to be wrong at 300 m
The mission brief is exact: autonomous survey of a 12 km export-cable corridor on Dogger Bank to 300 m depth, ≥ 8 h endurance, ≤ 0.5 m bathymetry resolution, one-dive coverage. Endurance, resolution and coverage pull against each other; the vehicle has to close all three at once, and every choice that gets it there has to be traceable back to that brief and forward to a test that proves it.
Baseline lifecycle, vehicle recipe
Carry the mission need to a released Technical Data Package: derive verifiable requirements, trade three hull architectures, converge the energy and hydrodynamic budgets, prove the models against a digital replica, then freeze the baseline.
- 01Frame the mission need and derive singular, verifiable requirements (endurance, resolution, coverage)
- 02Trade three architectures — Torpedo AUV, Open-frame hover, Hybrid glider-hover — scored on endurance 0.35, manoeuvre 0.30, payload 0.20, cost 0.15
- 03Record the decision: adopt the hybrid glider-hover configuration
- 04Converge the sizing loop — a 12.6 kWh battery pack against the ≥ 8 h endurance budget
- 05Close verification, freeze the baseline, and emit the Technical Data Package
Seeded demo ledger
PDR — Preliminary Design Review
The agent cannot pass PDR until a human has validated the items upstream of it and the platform's criteria are met.
- The sizing loop has converged
- Margins against every hard constraint are positive
- Every requirement traces to an architecture element that implements it
- A verification method is assigned to each requirement
The gate is a ledger item the agent cannot walk past — it stops an autonomous run from designing on top of an unreviewed baseline.
On the canvas




Bring a subsea autonomy system you actually build.
We will frame the need, derive the requirements, stand up the ELANG model and walk a review gate with you on the call.