Real World Event Sourcing: Page 105 of version 3 (PDF)
Inconsistent descriptions around whether Aggregates can process events or only commands.
An aggregate’s internal state can change by replaying events that predate the newly deployed aggregate, but that doesn’t alter the timeline, so it’s allowed.
The book seems to not be internally consistent with if aggregates are meant to process events or only commands.
Sometimes the book says that Aggregates execute commands to produce events (with Process Managers doing the inverse), but then quotes like this trickle through and I get a little confused.
I did look at the Commanded api, and it doesn’t seem to provide a way to process events in aggregates.