Architecture diagrams have a habit of going stale the moment you redraw them. The boxes stop matching the systems, the arrows stop matching the dependencies, and after a quarter or two the diagram has more in common with the vibe of the system than with the actual one.
Dinghy fixes that the same way Terraform fixes ad-hoc infrastructure changes: by treating the diagram as code.
The basic shape
Every Dinghy diagram is a tree of Shape components. Dependencies are part of the model, declared with _dependsOn / _dependsBy. Layout direction comes from _direction.
import { Shape } from '@dinghy/base-components'
