Thanks for taking the time to look at redux-machine and share your thoughts!

About the tiny code size: Redux sets a really good bar for small and simple code, so I tried to keep redux-machine small.

I agree that calling the key “status” is iffy, but couldn’t find anything better. Your suggestion of rmState might work, but state is already so overloaded and rm makes me think of removing stuff. One nice thing about `status` is that it’s singular and count, which hopefully makes it intuitive that a reducer can have only one status at a time but be in an state at all.