Skip to content

docs(event-storming): clear the Design-Level y-overlap and collapse the duplicate scheme #1789

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kyle-sexton merged 2 commits into from
Jul 30, 2026
Merged

docs(event-storming): clear the Design-Level y-overlap and collapse the duplicate scheme #1789

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7083f17
docs(event-storming): clear the Design-Level y-overlap and collapse t…
kyle-sexton Jul 30, 2026
32d006d
docs(event-storming): give Design-Level policies their own row
kyle-sexton Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 21 additions & 30 deletions plugins/event-storming/skills/simulation/reference/miro-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,44 +174,35 @@ Persona 1 sits at the `y=0` timeline baseline.

| Row | y | Purpose |
|-----|---|---------|
| BC Contracts (inbound) | -600 | Consumed events from other BCs |
| Read Models | -400 | Information panels |
| Actors | -200 | Who issues commands |
| Commands | -100 | Blue imperative actions |
| BC Contracts (inbound) | -1000 | Consumed events from other BCs |
| Read Models | -750 | Information panels |
| Actors | -500 | Who issues commands |
| Commands | -250 | Blue imperative actions |
| **Aggregates** | **0** | Light yellow — blank first, named last |
| Business Rules | 300 | Gray — invariants (stack at y=300, 550, 800) |
| Domain Events | 1100 | Orange — outcomes |
| Alternative outcomes | 1400 | Rejection/failure events |
| What-if challenges | 1700 | Red hot spots |
| BC Contracts (outbound) | 2000 | Published events |

**Main flow (y=0 baseline):**

- Commands, Events, Policies all sit on y=0
- Flow reads left-to-right, incrementing x by 400 per item

**Above the flow (negative y = up):**

- Actors: y=-250 (directly above their command)
- Read Models: y=-450 (above the actor)
- Hot Spots: y=-250 (above the related event)

**Below the flow (positive y = down):**
| Policies | 1650 | Violet — reactive `Whenever X, do Y` |
| What-if challenges | 1950 | Red hot spots |
| BC Contracts (outbound) | 2250 | Published events |

- Alternative outcomes: y=+250 (below the happy path event)
**Reading the layout:** every row's y comes from that phase's Y-Coordinate Table
above — negative is up, positive is down, and the bolded row is the baseline. The
tables are the only place y values are written down; nothing below restates them.

**Example: one complete flow segment**
**Horizontal placement:** the flow reads left to right, incrementing x by 400 per
item, independent of phase. A command and the actor that issues it share one x and
differ only by row, so a single flow segment is a column per step:

```
Read Model: x=0, y=-450
Actor: x=0, y=-250
Command: x=0, y=0
Domain Event: x=400, y=0 (happy path)
Event (alt): x=400, y=250 (rejection/failure)
Hot Spot: x=400, y=-250 (above the event)
Policy: x=800, y=0 (reactive — "whenever")
Next Command: x=1200, y=0 (triggered by policy)
Next Event: x=1600, y=0
Read Model x=0 row: Read Models
Actor x=0 row: Actors
Command x=0 row: Commands
Domain Event x=400 row: Domain Events (happy path)
Event (alt) x=400 row: Alternative outcomes (rejection/failure)
Policy x=800 row: Policies (reactive — "whenever")
Next Command x=1200 row: Commands (triggered by policy)
Next Event x=1600 row: Domain Events
```

**Legend frame positioning and sizing:**
Expand Down