Each part of the boat and its shore has a counterpart in the twin. Where it is software,
the twin runs the same software, unchanged. Where it is the world, the twin models it deterministically.
At sea
In the twin
Under the twin
Planner and autonomyPython, or a ROS 2 stack with Nav2
The same code, unchangedIn lockstep: it never runs ahead of simulated time.
Autopilot firmwareC, on the boat's microcontroller
The same source, built for the hostIn lockstep over a small C protocol.Roadmap: the unchanged binary on an emulated MCU
RadioRoIP on an NXP i.MX8M Plus, driving a marine VHF set
RoIP, unchangedBehind a virtual radio that answers its control frames as the real set does.
SensorsRadar, AIS, GNSS, camera, echo sounder, sonar
Deterministic sensor modelsDetection-level, with faults and GNSS spoofing.
Ocean and chartWaves, wind, current, tide; S-57 charts
Deterministic worldThe chart the planner believes, kept apart from the true seabed.
The air between radiosVHF over water
Deterministic RF modelPropagation, noise, squelch, capture, dual watch.
ShoreRelay server and operator consoles
UnchangedOperators work the twin exactly as they work the fleet.
Deterministic core
One run key. Bit for bit.
Integer-nanosecond event kernel, seeded randomness, its own maths. The same state hash on any machine.
↓
Oracles
Every run is judged
- Collision rules (COLREG)
- Closest approach
- Grounding, whole-hull clearance
- Lanes, restricted areas, arrival
↓
Evidence
Every failure is a file
Replay it, rewind it, shrink it to its cause, bisect it to the commit.