Proposal: Move orchestration to a middleware about satcheljs

[ericrallen]

I like the direction this is headed.

The old dispatch Action -> Orchestrator -> dispatch another Action -> Mutator pattern works fine, but this feels more intentional and explicit.

I'm assuming in this case any value returned from the before becomes the new actionMessage that is passed to the Mutator?

[Adjective-Object]

+1 to the explicit before and after in this proposal. I've seen instances where ambiguous execution order of orchestrators vs mutators leads to subtle bugs and hard to maintain code when orchestrators take data dependencies on the store.