Event Modeling

Produces a single visual blueprint of an entire system — one timeline read left-to-right that developers, designers, and stakeholders all share.

2 Core Ideas

Events on a timeline — The system is a sequence of business facts persisted over time. Events are the source of truth.
State for UIs — Users see views (screens, reports) built from events, not events directly.

Block	Color	What it is
Trigger	White	What starts a use case: UI wireframe, HTTP endpoint, or robot. Start simple — a named white box is enough
Command	Blue	An intention to change state, with parameters
Event	Orange	A business fact persisted. Past tense, business language, realistic data. Most important piece
View	Green	A read-only query that curates event data for a UI, report, or automated process

Not in the blueprint: Aggregates, entity diagrams, database schemas — those are implementation details.