The repository describes two modes: scene editing and scenario authoring.
Observed facts: The README says scene mode supports topology-aware lanes and exports to OpenDRIVE and Lanelet2. It says scenario mode lets users add events and triggers, then run esmini in the browser as WebAssembly and receive PASS/FAIL verdicts. These features connect visual authoring to executable scenario checks rather than treating the canvas as a static diagram.
Mechanism: The workflow links a structured scene representation to scenario events and a local simulation engine. Interchange formats and editable OpenSCENARIO files provide paths between the browser workspace and other tools; the stated browser-only design keeps files local rather than requiring a hosted backend.
Why now: The project is available as a public repository, and its described feature set makes browser-based scenario authoring a concrete option for teams evaluating autonomy-testing workflows.
Implications: For developers, the combination may reduce friction between sketching a road layout and replaying a test case. PASS/FAIL can aid iteration, but it is a tool-level verdict, not evidence that a scenario suite is complete or that a vehicle is safe.
Evidence boundary: These claims are based on the project’s GitHub README; they do not independently verify simulation fidelity, privacy behavior, maintenance status, or real-world validation.
Watch conditions: Look for reproducible comparisons of simulator output and documented test coverage, alongside independent reports on interoperability and privacy behavior.