I get lots of questions about process managers. Personally, I am not a big fan because:

• Processes are indeed everywhere
• Most processes are natural and not orchestrated
• Orchestration adds complexity

But, for the sake of it, I can try implementing it by adding some syntactic sugar to the existing building blocs:

• Aggregate -> Process
• AggregateState -> ProcessState
• ApplicationService -> ProcessManager

The manager needs to be called by a subscription. Possible by multiple subscriptions, but that can be done later. It also needs a producer to send commands. Here comes the question if I need to wire an existing app service that processes commands coming via HTTP also to consume command messages. It's possible even today, but maybe I can make it easier.

With a proper registration extensions, it should provide an easy to use API to wire all the things together.