The term "event-driven architecture" has a lot of people confused.
Events as state or events as notifications.
I see these two concepts lumped together all the time, but mixing them up is a shortcut to architectural turd pile.
Event sourcing uses events as the source of truth which you can derive state from.
Notifications use events to let other parts of the system react to something that already happened.
Same concept on the surface, very different design purpose underneath. And when those two get lumped together, it creates a lot of confusion about when each approach actually makes sense.