Reference

Board

Source BoardPage.tsx, MachineBoard.tsx, machineBoard.ts

/board and /board/{machine}. A machine written as features, drawn as the event-storming board the team would put on a wall, from operations.machineBoard. It is the same story the features tell, so it reads without knowing the code, and every note says which scenarios put it there.

The left of the page lists every machine the host registers. A machine that is not served from features has no board and is marked no board. With no machine in the URL, the page opens the first one that has a board.

The wall

One lane for the machine, and one more for each machine its rules reach, read left to right in the order the machine's states are reached. Each note is the colour event storming gives its role, and the role is written on it:

NoteColourWhat it is
AggregateLarge, pale yellow, first in its laneThe machine itself, with whoever starts it above
ActorSmall, yellowWho sends the command below it, or reads the view below it
CommandBlueWhat an actor or a rule asks the machine to do
EventOrangeWhat happened: a move from one state to another
PolicyLilacA rule: a guard on the command below it, a timer, or "when that machine gets here, do this"
ViewGreenThe read model: what people read, and who reads it, last in its lane

Each column is one command: the actors who send it, the rules that send or guard it, the command, and the moves it makes. A timer or a run's outcome that moves the machine with no command has a column of its own. A rule that starts a command in another machine draws an arrow from the event that sets it off to the rule, in the other machine's lane.

Arrows run down each column. An arrow to another column or lane would cross the notes between, so it is drawn only once a note at either end is clicked. The wall scrolls inside its frame, and a panel beside it stays in place: with nothing selected it lists every feature file behind the board and its scenarios, by file, line and name. Clicking a note lights up the notes it is linked to and lists the scenarios it came from; clicking a scenario lights up every note it put on the wall. A host file written without provenance draws the board and says it names no scenarios. Step text never reaches the console.

The machine's states and instances are on its page, linked from the board.