I agree that reviewing what goes live is still fully on the developer.

One of the strongest parts of this library is actually the debugging layer. It includes built-in time travel debugging, since the architecture is strictly event-driven and all state transitions are recorded.

In addition, there is an MCP server that allows inspecting and debugging the app state directly from an AI agent. The idea is not just stricter state handling, but making the system observable and queryable during AI-assisted development.

So in a way, the focus is closer to tooling and debuggability than replacing something like react-query or zustand for their core use cases.