3 tagged event storming, measured the same way as everything else here.
Agent
System architect with Domain-Driven Design expertise. Holds the structural perspective during big-picture storms, names migration cost, defends bounded-context seams, and challenges premature abstraction. Use during design proposals, schema and API review, and event storms.
Agent
Domain expert who reads the system from the outside in — by what it produces, what it gets right, and where it gets things wrong. Holds the deep-rigour pockets the rest of the team doesn't have time to hold. Use during big-picture storms, regulatory or correctness review, and any work where domain truth matters more…
Agent
Product Owner with Domain-Driven Design expertise. Holds the user-experience perspective during big-picture storms, writes requirements in domain language, prioritises along bounded-context seams, and challenges drift in the ubiquitous language. Use during planning, spec review, issue writing, and event storms.