Make sure re-sequencing can be easily handled by the framework. The easiest way to try and help implement this might be to handle all sequencing as "per block". This assumes oracle events are emitted in blocks too.
If everything is handled this way, then the resequencing can happen in the app layer (the app sorts events before processing). The only thing is that the app will need to track "blocks processed" in state, to ensure it's being submitted events on exact block boundaries. There's also then the question of how the app can tell what block an event belongs to.
The framework would just need to make sure it's always submitting events to the state transition function on block boundaries, which it already is.
Make sure re-sequencing can be easily handled by the framework. The easiest way to try and help implement this might be to handle all sequencing as "per block". This assumes oracle events are emitted in blocks too.
If everything is handled this way, then the resequencing can happen in the app layer (the app sorts events before processing). The only thing is that the app will need to track "blocks processed" in state, to ensure it's being submitted events on exact block boundaries. There's also then the question of how the app can tell what block an event belongs to.
The framework would just need to make sure it's always submitting events to the state transition function on block boundaries, which it already is.