Djinious
Subsea autonomyAerospace & marine

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.

DjiniousEngineering
The System Ledger canvas in DjiniousEngineering, shown on the Kestrel-SAR III project: lifecycle-stage columns from Mission & Need to Engineering Models, each headed by its ISO 15288 process and holding typed items tagged with their artifact type and evidence class.
ledger items seeded
40ledger items seededSeeded demo ledger
lifecycle stages populated
11lifecycle stages populated
system code
MRLN-XRsystem codeUK Continental Shelf — Dogger Bank

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.

Recipe and standards

Driven by the surface / subsea vehicle recipe — ISO 3691-4, COLREGs / IMO MASS Code.

MCA MGN 664

Carried as a standard the recipe honours for this class.

IMCA S 019

Carried as a standard the recipe honours for this class.

Marine Licence (MMO)

Carried as a standard the recipe honours for this class.

UNCLOS Art. 60/80

Carried as a standard the recipe honours for this class.

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.

  1. Frame

    Frame the mission need and derive singular, verifiable requirements (endurance, resolution, coverage).

  2. Trade

    Trade three architectures — Torpedo AUV, Open-frame hover, Hybrid glider-hover — scored on endurance 0.35, manoeuvre 0.30, payload 0.20, cost 0.15.

  3. Decide

    Record the decision: adopt the hybrid glider-hover configuration.

  4. Size

    Converge the sizing loop — a 12.6 kWh battery pack against the ≥ 8 h endurance budget.

  5. Release

    Close verification, freeze the baseline, and emit the Technical Data Package.

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.

Convergence

The sizing loop has converged.

Margins

Margins against every hard constraint are positive.

Allocation

Every requirement traces to an architecture element that implements it.

Verification method

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.

In the platform

The notebook view reads any ledger as a narrative of the thread — the same items, stage by stage, from mission need to the released package. It is shown here on the Kestrel-SAR III project.

DjiniousEngineering
A System Ledger in the DjiniousEngineering notebook view: the eleven stages listed on the left, and the Mission & Need items — a high-level specification and a mission brief — shown as spec_brief items with judgment evidence and Validate and Reject controls.
The thread read straight through, stage by stage, each item waiting on a human to validate or reject it.