experimentalE2
Problem
Workshop output often stays informal — whiteboard photos, loose markdown. Agents need a domain contract they can actually use.
Approach
A browser board for domain modeling. Export a schema-valid `.storm.json` (board-snapshot-v1): elements, relations, glossary, hotspots, optional event schemas. Data stays local in the browser.
Artifact
board-snapshot-v1 (.storm.json)
JSON Schema: https://abx-git.github.io/E2/schemas/board-snapshot-v1.schema.json — machine-readable domain context as agent input.
Mix methods as needed: Event Storming, DDD, BDD/Example Mapping, User Story Mapping, Event Modeling — on one board.
Typical path: workshop → model → export `.storm.json` → attach in the IDE as agent context (“implement aggregate X per the board”).