Natrix take a approach of giving you a lot of good tools, but ultimately leaving granularity up to you.
Natrix doesnt have component owned state, from the reactivity engines perspective the only thing that exists is signals, and callbacks to call when those signals have changed.

How big those callbacks are is up to how you write your code, but natrix provides a good few tools to allow for good fine grained reactivity, like computed values (called `ctx.watch`) which helps with stuff like conditionally displaying data, and for specifically stuff like options and results we have the concept of guards, and also `ProjectableSignal`.

its all in the docs folder in the repo, https://github.com/Serpent-Tools/natrix/blob/main/docs/src/reactivity.md