You are giving here some really nice tips about how to effectively write a Redux-based software. Hopefully I found this one before actually getting into the code, which saved me a lot of time.
But I’m wondering if the mutator concept (which is not part of ducks) isn’t a bit too much of abstraction. I know it’s important to decouple state logic from UI logic and to avoid repeating stuff but here we just kind of replacing single instructions by a pipe system + facades. I’m genuinely wondering if this is really necessary, if it really brings up some clarity.