Hi Vilian and Michael,
Michael’s assumption is right, an Aggregate, the Command Model in this case, will be automatically replayed based on the events which constitute all it’s changes.
Under the hood this is due to the usage of the EventSourcingRepository, which is the default repository used for Aggregates.
If you want to replay a given period of time however, you’ll have to set this up yourself.
This is usually not needed for your Command model, as you will execute Commands on a given Aggregate in the Command side of your application, which 9 out of 10 is against the current state of that Aggregate.
From a querying perspective this question makes more sense, as you might want to query a model on a given time stamp.
For that however, you’ll have to create something yourself.
Something along the lines of retrieving the stream of events and handling all the events until a given timestamp occurs, would be the most pragmatic solution I think.
You could also take the stance to store your query model at different points in time, so that you do not have to replay when the question occurs.
All of this depends on the exact use case at hand however.
Hope this helps, do not hesitate to post follow up questions!