event-storming-explorer

To extract domain subdomains from Event Storming, apply time-ordered clustering to past-tense domain events and actors. This process distills noisy Big Picture Event Storming sessions into clear subdomain candidates for subsequent classifiers.

Building an event timeline from Big Picture Event Storming involves extracting past-tense domain events and actors, then ordering them chronologically. The timeline excludes policies, commands, and system names to focus purely on domain events.

Yes, you can identify bounded context candidates for DDD workshops by clustering time-ordered domain events. This surfaces subdomain candidates from your Event Storming data, preparing them for later classification stages.

No, you do not include commands, policies, or system names when clustering event flows. The process strictly isolates past-tense domain events and actors to ensure the subdomain map remains free of technical infrastructure noise.

Mapping event flows and subdomain candidates generates two markdown artifacts: event-flow.md documenting the chronological event timeline, and subdomain-map.md detailing the clustered subdomain candidates extracted from the Event Storming session.