Inside the workbench.

The same Python runs natively on a workstation and, staged unchanged, under WebAssembly in a browser tab, separated by one function that asks which of the two it is in. Rendering is a pure software rasterizer, so nothing depends on a GPU being present to draw the interface, only to run the physics.

The object library, seafloor painting, the scene tree, a 2D plan viewport, the texture node editor, procedural and bottom features, the Fourier-wavefield parameters, run history, the output viewer, the validator, and the log all dock into one workspace. Undo and redo cover every gesture, grouped so that one drag is one undo.

A live validator runs twenty physics and geometry design rules against the scene as you edit, and blocks a run on an error rather than letting it fail forty minutes into a simulation. Vehicle tracks can be drawn freehand and are fitted to a spline, with altitude and speed per anchor and roll, pitch and yaw derived from a vehicle-response model.

Beyond authoring there are inspectors: a single-look-complex viewer with despeckling, a sub-aperture look sweep and a quadratic-phase-error tile readout, a side-scan waterfall, a mesh inspector, and a 3D scene view.