Maybe I'm confusing things but this events adapter is like simple Saga that by definition consumes events and produces commands. Of course, it does more as it also translates and serializes/deserializes but still if we talk about DDD maybe its good to name things as they are in DDD.
I think the event adapters are in an interface layer - translating incoming events / commands from different inputs to the application interface inputs
It's obvious while they are using Erlang as networking layer, they are not confident enough to leverage the whole Erlang OTP to solve almost all of the problems they have. How sad.
