When doing event sourcing, aggregate roots provide all of their state
changes to their repository. From the repository, the change events can
be persisted and pushed out to the reporting context. How does the
reporting context know which change events were processed as a
transaction in the domain?

I think this was discussed somewhere but I haven't been able to find it
so feel free to point me in the right direction (maybe one of Greg's
talks?).

Thanks