Event Storming Board

Each page imports the real components from $lib and renders them from the fixtures their tests use. Where a page shows something that is documentation rather than product — §01's swatches, §06's icon contact sheet — it says so on the page.

1. 01 Foundations Surface, ink, steel — the only non-sticky colors on the board.
2. 02 Sticky grammar Twelve types, canonical colors. Color carries meaning; nothing else on the board may use these hues.
3. 03 Anatomy & states One component, one geometry, twelve fills.
4. 04 Connectors Three types, one steel color, distinguished by line style. Never by hue.
5. 05 Board structure Lanes for the timeline, free zones for everything not yet placed.
6. 06 Canvas chrome Monochrome by rule, so the board is the only thing with color.
7. 07 Panels Where async rigor lives: detail, discussion, and the facilitator's review queue.
8. 08 Empty & onboarding A blank board asks one question at a time.
9. 09 Bounded contexts Who owns the language. A dashed steel region carrying a cloud mark; a flat-bottomed cloud once collapsed.
10. 10 Worked example — vendor onboarding change 22 steps, 4 phases, 6 context segments. Scroll right.
11. 11 Non-linear flow Parallel tracks inside a context. Structure that guides, not a grid that traps.
12. 12 Unknown & abstracted flow What we don't know yet, and what we have chosen not to show.
13. 13 Context map — the integration view Same model, zoomed out to the seams between teams. Contexts collapse to flat-bottomed clouds.
14. 14 Bounded context canvas Drill into one region. The ddd-crew canvas v5 layout, in this system's hand.
15. 15 Terms & definitions A dictionary per bounded context, read where the word is used.
16. 16 BPMN 2.0 view The same board in executable notation, and back again.
17. 17 Talking about an element One thread per sticky. People and the facilitator write in the same place.
18. 18 The facilitator A proactive actor with three interaction modes, not a chat box.
19. 19 Two primitives, five places The ordinal chip and the matrix. Build once, reuse everywhere.
20. 20 Ruled ground A third ground treatment: here, position carries a score.
21. 21 Naming the crossing The hollow square becomes the place the contract is written.
22. 22 Stakeholder map Influence against interest, on a 3×3 lattice. Ruled ground.
23. 23 Core domain chart A projection of the canvas chips. Classification by frame weight, never by fill.
24. 24 CML — the sixth tab A lossy export today. The parking tray is the honest part.
25. 25 Domain message flow — the messaging view One scenario, ordered messages between contexts, actors and systems.
26. 26 Do / Don't The two columns that close the document.