Events
Why are events described like this… “[Save Button] clicked]”… and not more like what you see in something like .NET.

For example, for “[Save Button] clicked]” you might have a generic Clicked Event, implemented by an object Button, that addresses the use case Save.

So instead of “[Save Button] clicked”, something like
"[click] {
"target": {
id: "#saveButton",
label: "Save"
},
payload:{
...entity-goes-here
}"

I like this because it means the events themselves can be well-defined and you can create interfaces around them. But in all the examples I see, and in this post, I never see anyone say/do this. So I think I may not yet see why this is not done here. Maybe it’s overkill?

Document Messages
I don’t think I understand what these really are. I read this as something an entity does once it’s been updated. In your example, I think this happens whenever there is a change to the ToDoList entity.

If this is correct, I am not sure why this is necessary because aren’t all objects interested in the the State of ToDoList already subscribed to it? What is listening for the Update Document Message that isn’t already somehow subscribed to the ToDoList data itself?

Commands
I use a Command to load a config file as part of my ngrx store implementation. In the Effect, it either dispatches a Success or Failure event. Is this the scenario you describe as being an example of what causes you to lose reactive control flow? What would you recommend instead?

Also at first, I thought I might want to simply use this Command to indicate that the state of the sender was READY to receive data (as opposed to explicitly naming “LoadConfig” (<- this could change). So instead of "[Application] LoadConfig" something like "[Application] Ready". Like I said above, this could be typed and assumptions could be made about what Ready means in a given context, but the sender doesn't have to care.

—

Thank you for any additional explanations.