doc-hub · event storming
Everything that happens, in order Domain events along a timeline, the actors and systems around them, and the disagreements nobody could settle — then commands and policies, then aggregates, as the room goes deeper.
What the colours mean Domain event Something that happened, in the past tense and in the business’s words. Actor A person or role who does something. External system Something outside the boundary that events come from or go to. Hotspot A problem or disagreement nobody in the room can settle. Opportunity Something worth doing that the timeline has made visible. Bounded context Where one model’s language stops and the next begins. The board needs JavaScript Notes are written and moved by hand, which is not something a page can do without scripting. The file format is plain text and is documented onthe format page , which needs none.
Nothing here is stored on the server — the board keeps a copy in this browser, and that copy goes no further. The .eventstorm file you export is the wall. The technique is written up in the development hub ; the seams found here become bounded contexts, and the work they imply is cut in the Story mapper . The format is documented , and the documentation portal holds the product catalogue.